Return-Path: <jhawk@MIT.EDU>
Received: from grand-central-station.mit.edu by po11.mit.edu (8.9.2/4.7) id AAA16758; Tue, 28 May 2002 00:47:14 -0400 (EDT)
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])
	by grand-central-station.mit.edu (8.9.2/8.9.2) with ESMTP id AAA11491;
	Tue, 28 May 2002 00:46:29 -0400 (EDT)
Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73])
	by manawatu-mail-centre.mit.edu (8.9.2/8.9.2) with ESMTP id AAA24528;
	Tue, 28 May 2002 00:46:29 -0400 (EDT)
Received: (from jhawk@localhost) by multics.mit.edu (8.9.3)
	id AAA27380; Tue, 28 May 2002 00:46:28 -0400 (EDT)
Date: Tue, 28 May 2002 00:46:28 -0400 (EDT)
Message-Id: <200205280446.AAA27380@multics.mit.edu>
To: network@mit.edu
cc: sipb-office@mit.edu
Subject: DHCP problems in W20?
From: John Hawkinson <jhawk@MIT.EDU>

Hi.

	A user came into the SIPB office reporting inability to
get a DHCP address on 18.187 (not using wireless). Her MAC address,
00023f73abe0, shows up as a registered one. She was running win XP.

Anecdotal discussion in the office suggests that there's been a
problem of this nature for some time; looking at the -i network logs:

| Auth: yes  Time: Fri May 17 11:57:50 2002 Host: TIR-NA-NOGTH.MIT.EDU
| From: Sam Hartman <hartmans>
| 
| I'm noticing some sort of problem with the DHCP servers
| trying to get a wireless address in w20.
| My client gets stuck in an offer->request loop
| but never gets an ack.
| Manually configuring an address works fine.
| I tried this with two different registered cards
| and got the same behavior

| Auth: yes  Time: Fri May 17 11:58:25 2002 Host: DRAGON-SLAVE.MIT.EDU
| From: recluse [7535255] <xiphmont>
| 
| I've witnessed a WinXP machine doing the same thing in the office a
| few days ago

| Auth: yes  Time: Tue May 21 21:36:57 2002 Host: OPUS.MIT.EDU
| From: Marc Horowitz <marc>
| 
| is there anybody around who can debug dhcp?  the mac address is correct,
| but it isn't working; another laptop on the same segment works fine.


Since no one seems to have formally reported this, I'm doing so now.
I haven't tried to reproduce it or to debug it or get traces,
though we can attempt to do so if asked.

The anecdotal discussion suggests it is a problem that principally affects
the wired network, and that the wireless network sees the problem to
a lesser degree. (I don't understand what would cause that).

--jhawk
