Re[2]: Microsoft Windows95 DHCP Timeout
Dave Pacheco <dave_pacheco@studio.disney.com> Thu, 29 February 1996 22:44 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25451;
29 Feb 96 17:44 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa25447;
29 Feb 96 17:44 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa15082;
29 Feb 96 17:44 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu;
(5.65v3.0/1.1.8.2/29Aug94-0956AM)
id AA21698; Thu, 29 Feb 1996 17:18:27 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4)
id AA29306; Thu, 29 Feb 1996 17:05:51 -0500
Received: from huey.disney.com by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA13629; Thu, 29 Feb 1996 17:05:47 -0500
Received: from studio.disney.com (cabinboy.wds.disney.com [153.7.4.17]) by
huey.disney.com (8.7.4/8.7.1) with SMTP id OAA02188;
Thu, 29 Feb 1996 14:03:41 -0800 (PST)
Received: from ccmsmtp2.wds.disney.com by studio.disney.com with SMTP id
AA10130 (5.65c/IDA-1.5); Thu, 29 Feb 1996 14:06:30 -0800
Received: from ccMail by ccmsmtp2.wds.disney.com (SMTPLINK V2.11 PreRelease 4)
id AA825631400; Thu, 29 Feb 96 11:43:07 PST
Date: Thu, 29 Feb 96 11:43:07 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dave Pacheco <dave_pacheco@studio.disney.com>
Message-Id: <9601298256.AA825631400@ccmsmtp2.wds.disney.com>
To: PradeepB@microsoft.com, "Alan S. Dobkin" <ADobkin@emory.edu>
Cc: DHCP-v4@bucknell.edu, USCLM@emory.edu, ISCLM@emory.edu, USDJD@emory.edu
Subject: Re[2]: Microsoft Windows95 DHCP Timeout
It has been my experience that the people at Microsoft that know about
DHCP are the NT group. I believe the code for Win95 DHCP was actually
taken from NT: unfortunately it was code older that the version that
has been fixed in NT to resolve this exact same issue.
- Dave Pacheco
______________________________ Reply Separator _________________________________
Subject: Re: Microsoft Windows95 DHCP Timeout
Author: "Alan S. Dobkin" <ADobkin@emory.edu> at FILM-INTERNET-BURBANK
Date: 2/29/96 11:33 AM
On Wed, 28 Feb 1996, Pradeep Bahl wrote:
> We have fixed this early timeout problem in Win95.
> Microsoft PSS can provide the fix.
Apparently PSS (assuming that means Product Support Services) doesn't
know anything about this. In fact, they don't seem to know anything at
all about DHCP. I've already had to explain what DHCP stands for and
what it does to two different technicians on the Windows95 support lines.
After spending over an hour on the phone, having to call three different
numbers, and talking with over six different people, I am very frustrated.
I apologize for venting to this list, but I hope that one of the Microsoft
participants can suggest a further method of action.
/--------------------------------+---------------------+-----------------\
| 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 |
\--------------------------------+---------------------+-----------------/
- Microsoft Windows95 DHCP Timeout Alan S. Dobkin
- RE: Microsoft Windows95 DHCP Timeout Pradeep Bahl
- Re: Microsoft Windows95 DHCP Timeout Alan S. Dobkin
- Re: Microsoft Windows95 DHCP Timeout Dave Pacheco
- Re[2]: Microsoft Windows95 DHCP Timeout Dave Pacheco