Name resolution timeout when using DHCP 2

[theoxyde]

This network is a strange setup so bear with me while I describe it:

I'm trying to track down a problem on an NT4 domain using an NT DHCP server. Some clients are still NetBEUI, but most have migrated to tcp-ip.

The problem is thus: some systems when obtaining their IP address through DHCP have trouble resolving names on the network, i.e., accessing their Exchange mailbox (takes a few tries). All of the affected systems are Win95. All other systems have no trouble. Oddly enough, when a static IP is used, the problem goes away.

This is an environment with 60+ systems on the network, with *NO* DNS or WINS servers at all. Could that be the problem, or is this more localized to a Win95+DHCP issue?

Any assistance greatly appreciated.

 

[GlenJohnson]

This is an environment with 60+ systems on the network, with *NO* DNS or WINS servers at all. Could that be the problem, or is this more localized to a Win95+DHCP issue? Does this mean only the win95 clients are having problems? You really should be using wins for any client's pre w2k. Try creating a simple batch file for the problem clients.

Ipconfig /release
Ipconfig /renew

Had to use this while working with a similar problem. Good luck.

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

http://www.johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

"Once the game is over, the king and the pawn return to the same box."

 

[theoxyde]

Does this mean only the win95 clients are having problems?
Correct. All other clients have no problems.

Thanks for the advice. I'll let you know if that corrects the problem.

 

[RichardHuang]

I highly recommend you install a WINS server in your network which will solve your problem permanently. A WINS server supports dynamic update and resolves Netbios name for win95/98 clients.

 

[GlenJohnson]

Correct, you should be using WINS for anything prior to W2K. If you can't afford a wins server, and your network is small enough, consider using lmhosts files. Throw one together, put it on a floppy and load it on all your clients in c:/windows. Good luck.

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

http://www.johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

"Once the game is over, the king and the pawn return to the same box."

 

[theoxyde]

Okay... releasing and renewing the DHCP leases didn't result in any change.

I've got WINS now running on a 2k Server and the server's address listed as the primary WINS on the affected client systems and the servers they commonly connect to. Again, this has not resulted in any change.

In my google-ing I have seen mention of a winsock update for Win95. I will try that next.

 

[theoxyde]

Winsock update + WINS == PROBLEM SOLVED.

The winsock update alone did the trick, but I figure the WINS server will stay as the clients feel a little more responsive in network apps when WINS is enabled.

RichardHuang:
While your suggestion of WINS wansn't the perfect answer, it was useful (as WINS has now been implemented)... so a star for you.

 

[theoxyde]

Woops. Glen did recommend WINS first... star for that too.

 

[GlenJohnson]

Glad things are working, that's what TT is all about.

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

http://www.johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

"Once the game is over, the king and the pawn return to the same box."