Thanks for the reply Andy,

I had actually tried the ignoredefaultroutes=enabled once before and it didn't 
work. I tried it again. Still didn't work.

I also disabled the IPv6 early in the experimentation but I did also disable 
the Link-Layer Topology and I set the NIC for 100Mbps Full Duplex. 
I disabled the public interface. I tried to remove the route 0.0.0.0 but it did 
not exist. Just for ha-ha's I removed all routes and then disabled and 
re-enabled the private interface. And ... No good. I still get an 
autoconfiguration address of 169.254.104.39

There are no switches or routers in between. In fact the DHCP server is on the 
same server as VMWare Server. 

Our guys are going to double check the DHCP config against the DHCP server that 
is working. All things being equal, if the public interface pulls an address 
without problem from the public DHCP server but the private interface has 
troubles getting an IP address from the private DHCP server than it might be 
the DHCP server? 


Thanks,
Adam


> -----Original Message-----
> From: Andy Kurth [mailto:andy_ku...@ncsu.edu]
> Sent: Tuesday, April 17, 2012 11:54 AM
> To: vcl-user@incubator.apache.org
> Subject: Re: Windows 7 and DHCP
> 
> A few things to try...
> 
> Run the following command and then try to get a private DHCP address:
> netsh interface ip set interface "<private interface name>"
> ignoredefaultroutes=enabled
> 
> This causes Windows to never route any traffic on the private
> interface through the default gateway.  The VCL capture code actually
> sets this to prevent known/common routing problems with Windows
> 7/2008.
> 
> If this doesn't help, try disabling the public interface and delete
> all default routes by running "route delete 0.0.0.0".  Try to get a
> private DHCP address.
> 
> Could also try:
> -Disable IPv6
> -Set a static speed and duplex for the interface
> -Disable Link-Layer Topology Discovery* on the interface
> 
> Are there any switches or routers between the Windows 7 computer and
> the private DHCP server?  I have seen posts discussing similar DHCP
> issues which were caused by the proxy arp configuration on a router.
> 
> Hope this helps,
> Andy
> 
> On Tue, Apr 17, 2012 at 9:57 AM, Hechler, Adam <hec...@rpi.edu> wrote:
> > Thanks Mike and Dmitri,
> >
> >
> >
> > As to Mike reply.  I've disabled the firewall completely, no help. I've also
> > set a static IP (with the one the DHCP server is offering) and I am able to
> > ssh from the management node to the vm.
> >
> >
> >
> > As to Dmitri's reply. I've checked out that KB article and added those
> > entries to the registry. No help.  There is no Relay Agent being used. The
> > DHCP server is the same subnet as the management node.
> >
> >
> >
> > Does anyone else have any other suggestions? How many of us are running
> > Windows 7 VMs with VMWare Server 2.x?
> >
> >
> >
> > Thanks,
> >
> > Adam
> >
> >
> >
> >
> >
> > From: Dmitri Chebotarov [mailto:dcheb...@gmu.edu]
> > Sent: Monday, April 16, 2012 12:45 PM
> > To: vcl-user@incubator.apache.org
> > Subject: Re: Windows 7 and DHCP
> >
> >
> >
> > Hi
> >
> >
> >
> > I have the same issue with DHCP, which seems to only affect Win 7 (32 and
> > 64). Linux and XP work OK.
> >
> >
> >
> > I've disabled dhcp broadcast flag
> (http://support.microsoft.com/kb/928233)
> > on both private and public interface on Win 7 image.
> >
> > Since then I get a lot less DHCP errors on Win 7 reservations, but still get
> > few once in a while.
> >
> >
> >
> > Looking at my dhcpd logs files it seems like Win 7 doesn't not accept
> > DHCPOFFER - I see multiple requests from Win 7, but it never gets IP
> > address. Even when I manually run ipconfig /release, /renew.
> >
> >
> >
> > Where is your DHCP server located?
> >
> > Is it on the same subnet/broadcast domain or you have DHCP Relay agent
> on
> > your subnet to communicate with DHCP server?
> >
> >
> >
> > Thanks.
> >
> >
> >
> >
> > --
> >
> > Dmitri Chebotarov
> >
> > Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
> >
> > 223 Aquia Building, Ffx, MSN: 1B5
> > Phone: (703) 993-6175
> >
> > Fax: (703) 993-3404
> >
> >
> >
> > On Monday, April 16, 2012 at 12:33 , Mike Haudenschild wrote:
> >
> > Hi Adam,
> >
> >
> >
> > Not to jump to the goofy, but could the Windows firewall be blocking it?
> >
> >
> >
> > Also, if you hand-assign an appropriate IP (disable DHCP on the adapter)
> can
> > Windows communicate properly on the interface?
> >
> >
> >
> > Regards,
> >
> > Mike
> >
> >
> > --
> >
> > Mike Haudenschild
> >
> > Education Systems Manager
> >
> > Longsight Group
> >
> > (740) 599-5005 x809
> >
> > m...@longsight.com
> >
> > www.longsight.com
> >
> >
> >
> > On Mon, Apr 16, 2012 at 11:52, Hechler, Adam <hec...@rpi.edu> wrote:
> >
> > Hi,
> >
> >
> >
> > We're having a similar issue that's been noted on the list before but I
> > can't seem to find if it was ever resolved. Here's a link to the archives
> > where it was discussed.
> > http://mail-archives.apache.org/mod_mbox/incubator-vcl-
> user/201104.mbox/%3C4DB59638.5000609%40ncsu.edu%3E
> >
> >
> >
> > Anyway,
> >
> >
> >
> > I have a Windows 7 base image (not captured yet). Both network interfaces
> > are set to DHCP. The public interface successfully grabs an IP address but
> > the private interface does not. All it does is assign on auto-configuration
> > address (169.254.x.x).
> >
> >
> >
> > We've tried the recommendation in the email message I linked to. Here's
> what
> > I see in the messages log:
> >
> > (note: I've changed the actual IP address offered to x.x.x.x - a real IP was
> > offered).
> >
> >
> >
> > Apr 16 11:39:45 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:39:45 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> > Apr 16 11:39:48 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:39:48 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> > Apr 16 11:39:56 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:39:56 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> > Apr 16 11:40:11 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:40:11 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> > Apr 16 11:40:44 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:40:44 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> > Apr 16 11:40:48 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:40:48 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> > Apr 16 11:40:56 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:40:56 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> > Apr 16 11:41:12 vclserver dhcpd: DHCPDISCOVER from 00:50:56:1a:01:11 via
> > vmnet1
> >
> > Apr 16 11:41:12 vclserver dhcpd: DHCPOFFER on x.x.x.x to 00:50:56:1a:01:11
> > via vmnet1
> >
> >
> >
> > Anything else I should be looking at?
> >
> >
> >
> > Thanks,
> > Adam Hechler
> >
> >   Senior Analyst /
> >
> >     PC Systems Administrator
> >
> >       hec...@rpi.edu
> >
> >         (860) 548-2446
> >
> >            Rensselaer at Hartford
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >

Reply via email to