Computing.Net > Forums > Windows Server 2003 > Unable to connect to server 2003

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Unable to connect to server 2003

Reply to Message Icon

Name: beff
Date: May 7, 2006 at 06:17:11 Pacific
OS: server 2003 r3 evaluation
CPU/Ram: amd athlon 2400+
Comment:

I'm running an evalutation version of windows server 2003. I've installed active directory and dns but have been unable to log on with an xp pro computer.

From the server I can ping everyone on the netowrk but the cannot ping the server from any other computer.

I can't ping it by its fqdn

I did make an account to log in on the server(ad - both user and computer), but the client can't even find the domain to join.

I do have dhcp running, but i also have it running on the router (linksys) but i assigned the server a specific ip from the router. (i also tried have it assigned automatically from the router but that didn't work either)

No errors show in the event viewer.

Any help would be appreciated, thanks!



Sponsored Link
Ads by Google

Response Number 1
Name: heropsycho2177
Date: May 7, 2006 at 08:06:44 Pacific
Reply:

Is the server pointing to itself for DNS?

Is the client pointing to the server for DNS?

"Milk was a bad choice!"


0

Response Number 2
Name: beff
Date: May 7, 2006 at 08:43:44 Pacific
Reply:

the server is point to these addresses for dns:

194.25.0.68
194.25.0.60
194.25.0.52

i don't know where these address came from.

The servers address is 192.168.0.108

The server used to also look to itself for dns but i removed the static ip when trying to troubleshoot.

The client used to have the server listed as one of its dns when i ipconfig /all but is not currently doing so. the client is using the router for dns.



0

Response Number 3
Name: heropsycho2177
Date: May 7, 2006 at 09:29:38 Pacific
Reply:

Both server and client must point to the server as its DNS server. That's a non-negotiable.

"Milk was a bad choice!"


0

Response Number 4
Name: heropsycho2177
Date: May 7, 2006 at 09:49:04 Pacific
Reply:

"I do have dhcp running, but i also have it running on the router (linksys) but i assigned the server a specific ip from the router. (i also tried have it assigned automatically from the router but that didn't work either)"

Whoa, whoa!

The DC should have a static IP. DO NOT set it to obtain an IP address automatically, even if you set it for a reservation in the DHCP server, that's still an exceptionally poor idea.

Secondly, you should only have one DCHP server per broadcast domain, so you need to turn off one of those DHCP servers.

Whatever DHCP server you have should again be giving out your DC's IP address as the DNS server to use. Set DNS in the DC under forwarders the ISP's DNS servers.

"Milk was a bad choice!"


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Unable to connect to server 2003

Unable to install Win server 2003 www.computing.net/answers/windows-2003/unable-to-install-win-server-2003/3166.html

migrating from P2P to Server 2003 www.computing.net/answers/windows-2003/migrating-from-p2p-to-server-2003/5154.html

remote desktop connection to server www.computing.net/answers/windows-2003/remote-desktop-connection-to-server/6336.html