• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2k3 Server Name resolution problems

N

nweaver

Diamond Member
Windows 2k3 server, (pushed down via an image from Altiris) on an HP workstation (2.66 Ghz, 256 MB ram, onboard Broadcom 440 10/100 NIC).

I cannot ping "www.google.com", it instanly comes back saying it cannot resolve the name

I CAN ping google via IP address

I CAN resolve google's name via nslookup on that machine

I have used 2 different DNS servers (one was project specific, but still forwarding requests to our main servers, and our main DNS servers)

Other machines do NOT have this same problem (can ping via fqdn)

It's strange, because it doesn't even seem to try and resolve the hostname when typing "ping www.google.com". It instantly fails.


Any ideas?
 
If it's immediatly failling it's probably not a connectivity issue (because that would require you to wait for timeout). I would review your TCP/IP DNS config to see if something is setup wrong.

Might also want to post your ipconfig /all
 
Don't have that box right here (to lazy to run over there before heading home) but I using DHCP atm to do DNS, and every other box works.

Basics are:

IP 216.119.202.220
Subnet Mask: 255.255.255.0
Gateway: 216.119.202.XXX
DNS: 216.119.206.253, 216.119.203.253


NSlookup pulls the default server from the IP settings, and it works, so I would assume normal name resolution would work. Anything else?
 
I using DHCP atm to do DNS, and every other box works
Click to expand...
Well that really limits it down, definetly a strange issue if you can resolve hosts from nslookup but not when pinging. Have you verified there isnt a hosts file screwing things up? nslookup queries the dns server directly so it would not be effected if that was the case. Just trying to come up with an explination for the symptoms you are describing.

When you are at that box (maybe tomorrow) can you grab a screen shot of the tcp/ip>advanced>dns tab? I'm just looking for something out of the ordinary.

-Erik
 
I'm really not sure. I stopped it on my box and flushed the cache and was still able to ping google. Just tossing out ideas.
 
I'll get a screenshot tomorrow. Not a hosts file problem (unless it's ONLY checking that). I'll check the DNS client service as well.
 
i know it seems obvious but have you flushed the DNS cache?
ipconfig /flushdns

ipconfig /registerdns?


hope you get it up and running.

good luck
 
Originally posted by: jpbelauskas
i know it seems obvious but have you flushed the DNS cache?
ipconfig /flushdns

ipconfig /registerdns?

good luck
Click to expand...

What he said... had something similar on a 2k3 box last week.
 
The nice thing about network issues is that you can always take a network trace and find out EXACTLY what is happening behind the scenes. If you can't solve the problem, get a network trace and look for the DNS request and response packets.
 
Check your router or gateway settings. Where is your server sending its requests to resolve internet addresses? Your dns server has to be forwarding its internet dns requests somewhere to have them resolved. That sounds like your problem. Is your isp having dns problems?
 
If you can ping google, and ping your dns server, and do an nslookup that tells me everything in the world is working right. If you were to query a dns server for google you should get an answer but you aren't. What's the logical reason? .. You aren't really querying the dns server.

post an ipconfig /all for us.


If you would like you can take a quick trace with netmon (if not in administrative tools, install it via windows components) and send it to me. I'll PM you my address. I do networking at MS and look at those things all day long.


to answer someone's earlier question: You can do an nslookup even if you don't have a dns server set in tcp/ip. nslookup is just a standalone app that requires IP to be loaded.
 
status...
busy and moved on for the moment 🙂

I'll see if someone is going to be using that image this week, and if they push it down and have the same problems, I'll jump back in with stuff. A sniffer trace is the first thing I'll do (but not sure how to use netmon, I'm an ethereal type of guy) and go from there.

Just for those who are asking questions, remember this: Network is WORKING (I can ping, via IP, any IP address, such as gateway, dns server, google.com via IP)
DNS servers are working (hundreds of other boxes every day use them...and nslookup works)
DNS is correct in IP settings (both static and dhcp, nslookup works fine)
name resolution fails in both IE and vi a ping (ping www.google.com fails instantly with a "cannot resolve name" type error)
 
Originally posted by: NogginBoink
The nice thing about network issues is that you can always take a network trace and find out EXACTLY what is happening behind the scenes. If you can't solve the problem, get a network trace and look for the DNS request and response packets.
Click to expand...

Except when you're using IPSec 😉
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top