Win98 workstations cannot ping Win2kServer 1

[Ianmac09]

I have just upgraded(?) our 1 and only fileserver to Win2K server, it was NT4 and I did a clean install. Setup all went okay (domain name same as before for pre win2000 computers), did DNS and set server IP to 192.168.100.10 (same as before) but I cannot get any of the (WIn98se) workstations to log on (accounts/passwords etc are all checked & correct). The weird thing is that if I try to ping the server from a workstation (192.168.100.25) it times out, I then ping server to workstation and is okay, I then ping workstation to server again and it works okay??
I have checked rebooted and repeated this several times. Some of the other wkstns cannot ping server at all, and others can ping but not log on. All have identical TCP/IP setups;- 192.168.100.**, subnet 255.255.255.0, primary & Secondary DNS set to external internet provider IP's, default gateway 192.168.100.1 - router internal IP.
I have to re-check the time synch as this may be out but does this affect ping??
Netbios is enabled over TCP/IP on wkstn as per previous working (NT4 Server) config.
Help, anybody (this is driving me nuts and I want to go and be a emu farmer instead).

Thanks

 

[bogie]

Pre-w2k systems will need a wins server configured and running on the w2k server. Also you should have a DNS server running on the w2k server with fowarders set to your ISP's DNS server. The workstations should point to the w2k as there DNS server.

I had the same type of logon problems with w98 systems until I setup a wins server. Not shure whats going on with the pinging IP issue.

 

[AlexIT]

Ok, bogie is correct in that you should run a DNS server (but I'd avoid a WINS server.) Your network has no name resolution at the moment, so the client is asking your ISP what the server name is...and they don't know this.
If you installed Active Directory (which you need for domain client accounts), then you have DNS running on your server already. If you didn't do this (answered other than "This is the only server in my network" then you should run DCPROMO to get AD installed. AD requires DNS, so the wizard will also install and configure DNS services. Your server NIC has IP 192.168.100.10, subnet 255.255.255.0, change DNS to loopback address (127.0.0.0) and leave gateway set for your internet router IP 192.168.100.1.
Workstations have 192.168.100.**, subnet 255.255.255.0. Change workstation primary DNS to your server IP 192.168.100.10 and do not enter any secondary. The default gateway is still your router IP 192.168.100.1.
Go in the DNS server, you do not want a root zone "." domain, so make sure this isn't listed (delete it if you find one) and set forwarders to your ISP's DNS servers. (If you have more than 10 clients, I'd recommend setting up DHCP on the server for addressing also.)
In the above fashion your workstations will receive all name info from your DNS server, which asks the ISP only for external internet addresses.

Look for "DNS question" post by mattwray, we covered the preferred (by me anyway) single server setup in there pretty well...

Alex

 

[ShackDaddy]

WINS settings will have nothing to do with ping unless all other methods of resolution (broadcast, hosts, DNS) have failed.

Assuming that it's not as bad as all that, this sounds like a problem on the data-link layer of your network. Does your switch have any static MAC mappings? When you upgraded the server, did it get a new network card? Have you tried clearing the mapping database on your switch? If this is the problem you could prove it by putting your server and a couple of workstations on a hub and then pinging from the workstations successfully.

ShackDaddy

 

[tlcscousin]

Did you have all the clients go back to workgroup then join the new domain?
"I have just upgraded(?) our 1 and only fileserver to Win2K server, it was NT4 and I did a clean install."
Using the same domain name is ok, but the clients will still be looking for the old domain server.