Software

Ask something
Question Locked

PC unable to resolve a single domain name

0 helpful
8 replies

by dmambo

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a user unable to resolve a single domain name using IE7 and FF. This is our corporate domain, so it's not blocked in any way. Other users logging in to this XP SP3 machine have the same problem and if the primary user of this PC logs in to another PC, there are no problems.

I flushed the DNS cache, added the domain to the hosts and lmhosts files, ran WinsockXPFix, scanned for malware.

He can hit the site by IP address, but can't use any of the links on the site because they're all specified by URL. No other sites give any problems.

Any suggestions on how to resolve?

8 replies

by ---tk---

I would try (might have already done this), right click the LAN connection in network connections, General tab > TCP/IP > properties > General tab - Advanced > 3rd tab WINS > make sure Enable LMHOSTS lookup is checked.

by dmambo

Any other suggestions? This is really pissing me off!

As a workaround, I'm having the guy remote into an F/P server and using IE from there, but I HATE doing that.

by cg it

did you put the right DNS server address in the NIC properties?

by ---tk---

uninstall and reinstall the NIC in device manager? That usually resets everything...

Added: What happens when you run a nslookup on any server?

by ---tk---

I would place the PC into a workgroup, delete it from AD (Users and Computers), and join it back into the domain. Tried that?

by cg it

He can hit the site by IP address, but can't use any of the links on the site because they're all specified by URL. No other sites give any problems

if you can get to a site by ip address but not name, then it's a DNS problem.

The DNS problem can be a forwarding problem,eg the DNS server the client uses for name resolution doesn't forward the query to other DNS servers for resolution, a DNS problem eg the DNS server the client uses has no DNS record for that address nor does any other DNS server that the query has been forwarded to, or a client problem using the wrong DNS server for name resolution which can not resolve the name and no other DNS servers forwarded the query can resolve the name to an address.

bottom line is a DNS problem because the name isn't resolved to an address.

This discussion is closed to new replies.