Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems Joining Domain

Status
Not open for further replies.

SqueakinSweep

Programmer
Jun 20, 2002
945
0
0
GB
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
 
Sweep did you test the TCP/IP stack ?

Ping 127.0.0.1

Have you tried to renew the Ip address from the dhcp server.

I am assuming that the Pro machine is not even getting an IP address.

If that is the case, I would say go for another Network Card I have had 4 not work on me before.

Did the Xp machine work off the same cable connection as the Pro machine.

Just some ideas





Regards

Jonno BrainDump Specialist
MCSE(NT) MCSA(2k) CCNA
 
Jon

XP machine worked off same cable connection
The PING you suggest, is that from the Server or Pro m/c?

I have some new NIC's on order to collect, and will try them out.

Thanks for the suggestions.





Sweep
...if it works dont mess with it
 
127.0.0.1 is the network cards IP address - like a loopback address

obviously the server is ok and the cabel if other clients connect from it.

if you can ping 127.0.0.1 from win 2k then that proves the network card is working.

If its connecting at 10mbps on the same cable as the client that was getting 100 and also assuming the pro machine is not getting an IP then check the network card settings on the pro machine are set to 100 full duplex cos some switches can be configured to only connect at a certain speed.

Good luck
 
Can you post an IPconfig from the XP box and the pro box for comparison?

Regards,
Lightspeed1
 
Ok...here's the state of play. Have now installed new NIC, which is better as its at 100M instead of 10M. Still no luck. I can ping 127.0.0.1 successfully, cant ping 10.10.1.1 which is the Server/DNS address. I tried changing the server address to 10.10.1.2, and then I managed to ping it. I didnt however change the DNS address. Im reluctant to touch the server settings as I had no problems connecting from XP.

I have tried on my W2K Pro, to assign an IP address in the same range, and tried auto assign, tho for some reason I just cant ping 10.10.1.1 (DNS)

Resonate...card is set to Auto Detect.
Lightspeed1...I will check out IPCONFIG settings and repost later.

Another thing Im unsure about...
My Server is named quite uninventively WSERVER
My Server Domain is named DOMAIN (yawn!)

When I look at DNS and drill down, the DNS Name seems to be
DOMAIN.local. I assume I only have to enter the Domain name as DOMAIN when trying to join the DOMAIN from Pro. Im clutching at straws here I guess, unless I can ping it, I have little chance of success.

Thanks for all your posts, its given me much to think about.






Sweep
...if it works dont mess with it
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top