Microsoft Windows95 DHCP Timeout

"Alan S. Dobkin" <adobkin@emory.edu> Thu, 29 February 1996 01:11 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06777; 28 Feb 96 20:11 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06773; 28 Feb 96 20:11 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa17801; 28 Feb 96 20:11 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu; (5.65v3.0/1.1.8.2/29Aug94-0956AM) id AA25517; Wed, 28 Feb 1996 19:54:07 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4) id AA18430; Wed, 28 Feb 1996 19:44:33 -0500
Received: from curly.cc.emory.edu by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA03475; Wed, 28 Feb 1996 19:44:32 -0500
Received: from curly.cc.emory.edu (adobkin@curly.cc.emory.edu [170.140.1.66]) by curly.cc.emory.edu (8.7.3/8.6.9-950630.01osg-itd.null) with SMTP id TAA14711; Wed, 28 Feb 1996 19:44:18 -0500 (EST)
Date: Wed, 28 Feb 1996 19:44:14 -0500 (EST)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Alan S. Dobkin" <adobkin@emory.edu>
X-Sender: adobkin@curly.cc.emory.edu
To: DHCP-v4@bucknell.edu
Cc: "Craig L. Myers" <USCLM@emory.edu>, "Carol L. Moretto" <ISCLM@emory.edu>, "Darrell J. Durggin" <USDJD@emory.edu>
Subject: Microsoft Windows95 DHCP Timeout
Message-Id: <Pine.SV4.3.91.960228193515.23033P-100000@curly.cc.emory.edu>
Organization: Emory University
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Since we're on the topic of Microsoft's DHCP software, I thought I'd ask 
this group (and specifically the Microsoft folks) for some help with this 
problem.  We are currently testing Sun's SolarNet PC-Admin 1.5 server for 
use as a campus-wide DHCP/BootP server at Emory.  So far, I have had 
success using DHCP with Windows95 in the same subnet as the server, but 
the negotiation fails if the Windows95 client is in a different subnet, 
using the helper-address function of our Cisco routers.  Incidentally, 
Apple's Open Transport client works using the same server in either the 
same subnet or accross the router.  Specifically, the Windows95 client 
sends the DHCP request, the router passes it on, the server sees it and 
responds with an IP number, but the Windows95 client states that it has 
not gotten a response.

After doing some research, I've noticed that a similar problem has been 
posted to the Windows95 Networking Bugs FAQ.  Has Microsoft addressed 
this problem?  Is there a solution?

http://WWW-Leland.Stanford.Edu/~llurch/win95netbugs/faq.html
http://WWW-Leland.Stanford.Edu/~llurch/win95netbugs/faq-c.html#c28

C.28. What do I do if Win95 won't wait long enough for my DHCP server to 
assign an address?

Date: Mon, 6 Nov 1995 10:55:17 -0600
From: David Devereaux-Weber <djdevere@facstaff.wisc.edu>
Message-ID: <199511061655.KAA73144@audumla.students.wisc.edu>

[Complain, I guess, until Microsoft fixes this.] 

We have had difficulty with Microsoft's implementation of DHCP in WIN95. 
the DHCP client is supposed to wait a reasonable period of time for the
server to check an address before it is given to the client. Microsoft's
client doesn't wait very long - it bails out early and reports no
response. The people at Sun hacked their client software for us to
temporarily work around the problem. Unfortunately, trying to get
Microsoft to understand and support the official protocol has been
unsuccessful to date. 

/--------------------------------+---------------------+-----------------\
| Alan S. Dobkin, LAN Specialist | 1784 N. Decatur Rd. | E-Mail Address: |
| Networked Workstation Support  | Suite 300 (3rd Fl.) |     ADobkin     |
| ITD Network Systems, Emory U.  | Atlanta, GA 30322   |   @Emory.Edu    |
| <URL:http://NWS.CC.Emory.Edu/> |  (404) 727-2766     | FAX #: 727-0817 |
\--------------------------------+---------------------+-----------------/