General discussion

Locked

Name Resolution

By christieno ·
Here's the deal. I have a 25 person network running NT 4.0 with DHCP and WINS. A handfull of computers (mostly Win95) are having difficulty with name resolution, specifically with the servers name. This is causing problems when they attempt to access the Exchange Server through Outlook 2000. Just about all of them can get through when they click on "retry". Now from the server I can ping the PC's by name and from the PC's I can ping the other PC's on the network by name relatively quickly. On the handfull I am referring to, when I ping the server by name it takes 30-40 seconds to resolve the name to an IP address. I'm stumped. Please help.

This conversation is currently closed to new comments.

17 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Name Resolution

by Geppetto In reply to Name Resolution

Sounds like you have problem with your browser services. You can try to see which server/workstation is trying to run as master browser and work in that direction. Otherwise, you can try to use lmhosts file in your workstation. LMHOSTS file can directly link up your servers and workstations. Furthermore, you can use login script to control distribution of revised lmhosts file.

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Collapse -

Name Resolution

by stuart.clark In reply to Name Resolution

Sounds Like you migth have some static entries within the config of some of your computers. ie hosts/lmhosts.

It might be worth changing the node type of your client machines to a Hybrid node, you can do this from inside DHCP Manager. This will force the computers to resolve to WINS before going to static files and broadcasts.

Or

Check that the wins server does not have any static mappings pointing to another location on the network.

Stuart.

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Collapse -

Name Resolution

by Curious_George In reply to Name Resolution

Your question did not mention whether or not you are using DHCP to configure workstation WINS server settings, if you are not, it can and should be used. Additionally, any entries that are manually entered on the workstation, over-ride entries provided by the DHCP server so my question to you is, "Do any of the problem workstations manually configured to use an incorrect WINS server, or do they have any WINS server enties at all, or are the configured to use DHCP server for acquiring a WINS server IP? (It is optional).

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Collapse -

Name Resolution

by jeromey In reply to Name Resolution

We had a similar problem here. I have a feeling it has to do with the order of name resolution, (plus the fact that one version of MS TCP/IP had a bug in its order of name resolution). Setting up an "intranet" DNS server will likely provide a good workaround to your problem. You also might find this knowledge base article helpful:
http://support.microsoft.com/support/kb/articles/Q172/2/18.asp?LN=EN-US&SD=vap&FR=1
(you will have to reconstruct the URL or query for article Q172218

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Collapse -

Name Resolution

by curlergirl In reply to Name Resolution

This usually occurs when you have Win95 PCs that connect to an Exchange Server and are also using external (i.e., ISP-based) DNS server IP addresses. The best/easiest solution I've come up with is to add a HOSTS file to the workstations. On Win95,the HOSTS file resides in the C:\Windows directory; on Winnt, it's in the \%systemroot%\Winnt\system32\drivers\etc directory. You'll find a file called HOSTS.SAM that you can use as a basis. Just open that file, add a line to the end of the file with the IP address and name of your Exchange Server, then save the file as HOSTS - WITHOUT any extension. Instant Fix!! You can add an internal DNS server like someone else suggested, but this is a lot of work for such a small problem. Hope this helps!

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Back to Windows Forum
17 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums