I think you will find the trouble (whatever it is) is with your W2K Clients.
Sorry but I can't tell you exactly where to look.  IPConfig /All is your
diagnostic tool.

What else do you W2K desktops have in common?  By chance are they all on the
same subnet?  If yes, think IP Helper (in Cisco terms).

FWIW.
We have a Lucent QIP DHCP Server running on Solaris.  It supports our AD
Forest consisting of W2K DCs, W2K Member Servers, NT4 Member Servers, XP
Desktops, W2K Desktops, NT4 Desktops, W9x Desktops.  There were no OS
specific settings needed on the DHCP Server to support our differing
clients.

Bob

-----Original Message-----
From: Ronnie Corbin [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 17, 2003 9:56 PM
To: NT 2000 Discussions
Subject: W2K Pro DHCP incompatibility issues with WNT Server 4.0

I have a network consisting of Windows NT 4.0 servers, Windows NT 4.0 W/S
clients and W2K Pro clients.  The problem I'm having is the W2K Pro
clients cannot obtain a lease from the WNT Server DHCP server, although
the WNT 4.0 W/S clients have no problems obtaining or renewing a lease. 
I've went so far as to install a W2K Server DHCP server on the LAN, but I
have the same problem with the W2K Pro clients. I haven't had any luck in
researching this on TechNet.  Any help would be greatly appreciated.  R.

------
You are subscribed as [EMAIL PROTECTED]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to %%email.unsub%%

CONFIDENTIALITY NOTICE: This E-Mail is intended only for the 
use of the individual or entity to which it is addressed and 
may contain information that is privileged, confidential and 
exempt from disclosure under applicable law. 
If you have received this communication in error, please 
do not distribute and delete the original message.  
Please notify the sender by E-Mail at the address shown. 
Thank you for your compliance.

------
You are subscribed as [EMAIL PROTECTED]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to