SqueakinSweep
Programmer
I have a newly setup W2K Server, which is to be the only server, and is set as the primary domain. I simply let W2K Setup do its stuff, and configure AD,DNS and DHCP.
Im trying to connect to it from a W2K Pro Client. I can't ping the server now, although I could at one point, and it wont find the domain. However I find that I can connect to to a drive on the Server quite happily using NET USE. I have configured the DNS to point to the server DNS, but if I cant PING it, its hardly going to find it!
I tried connecting an XP configured laptop to the server, changed the DNS lookup, and bingo..no problem. So the problem appears to be with the W2K Pro machine. The oldy difference I can see is that this machine only connects at 10Meg.
Can anyone offer any advice of what to try next, or what to investigate?. I just simply want to join the domain, and would expect to see a DNS entry on the Server when I do so. I suspect a dodgy NIC card, even though I have tried two different (if old) cards on the client.
Sweep
...if it works dont mess with it
Im trying to connect to it from a W2K Pro Client. I can't ping the server now, although I could at one point, and it wont find the domain. However I find that I can connect to to a drive on the Server quite happily using NET USE. I have configured the DNS to point to the server DNS, but if I cant PING it, its hardly going to find it!
I tried connecting an XP configured laptop to the server, changed the DNS lookup, and bingo..no problem. So the problem appears to be with the W2K Pro machine. The oldy difference I can see is that this machine only connects at 10Meg.
Can anyone offer any advice of what to try next, or what to investigate?. I just simply want to join the domain, and would expect to see a DNS entry on the Server when I do so. I suspect a dodgy NIC card, even though I have tried two different (if old) cards on the client.
Sweep
...if it works dont mess with it