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.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Name Resolution

by shardy In reply to Name Resolution

A couple things come to mind as I have experienced this one often. First look at the client machines .If you have only one wins server,be sure that the secondary wins server entry is NOT empty.Put the first entry in again,if necessary.Also two distinct wins servers are in order,especially if the wins server is a busy server. I cured a slow wins problem at my site by defragging the data drive on the wins server ! Also,if you are using wins resolution with dhcp specified (hybrid )type (46)resolution,host resolution via host and lmhosts will be at the bottom of the resolution order,
If all else fails or you want to setup a workaround,simply put the ip address in the mail profile at each of the 95 clients

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Collapse -

Name Resolution

by TechStop In reply to Name Resolution

A previous responder stated that he thought you might be having a problem because of someone's external DNS server entries (if I'm remembering that post).

If that's your problem, this sort of thing can be overcome by having your own DNS server,which is set up so that if it can't resolve a name itself, it forwards the request to another nameserver. So your Win clients should have your nameserver(s) listed as their first (not only) choice; they'll get a quicker response when using DNS for resolution. This assumes the poster I referred to is correct about the source of your problem. You didn't mention DNS (although that's how I'd be resolving in this situation), only WINS.

Another thing to check is---and nearly all of my experience is with NT, so it might not apply to Win9x---what is the binding order for protocols on your adapters? If you're using TCP/IP and some other protocol (NetBEUI, etc.), then make sure TCP/IP is first or "top of the list" in the binding order. This speeds resolution,

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Collapse -

Name Resolution

by TechStop In reply to Name Resolution

Oops...went over weird 1000 limit. Anyway...speeds resolution.

A final thought I had was on the resolution order. In Win95, I believe this is broadcast-WINS-DNS-lmhosts. This can be changed in the Registry, but I forget how right now.

Don't know if I've been helpful, but I thought I'd try.

Collapse -

Name Resolution

by christieno In reply to Name Resolution

The question was auto-closed by TechRepublic

Collapse -

Name Resolution

by christieno In reply to Name Resolution

This question was auto closed due to inactivity

Related Discussions

Related Forums