Dhcp issues / settings

Until 2 weeks ago dhcp worked fine using range 10.0.0.3-255, subnet mask255.0.0.0, and default gateway 10.0.0.254 and dns server 10.0.0.3 We have about 40 macs and the same no of pcs. The pcs have started showing the following settings ipaddress 192.168.1.73 eg subnet 255.255.255.0 default gateway 192.168.1.1 dhcp server 192.168.1.1 dns servers 64.86.133.51 and 63.243.173.162. The macs are unable to log onto the network for the same reason and I have had to assign a static address to the various computers to get round this problem. It happens when they have been switched off on are unable to see the network on startup.
Any ideas what is going on.
Al

Doing a search on the DNS IP's shows hits about DNS changer viruses.
http://www.tek-tips.com/viewthread.cfm?qid=1538656&page=1
You might actually want to run a virus scanner on your PC's. If you don't have an up to date version, there are free scans out there.
http://housecall.trendmicro.com/
JL

Similar Messages

RV042 DHCP Gateway Settings

I have a core routing switch along with my RV042. I am using the RV042 for DHCP, BUT I would like to issue a different default gateway than the router itself. I'd rather give the address of the core switch as the default gateway to my DHCP clients as I have to route to various other VLAN's. Instead now I have to do static routes in the RV042 to get back to those when it would be cleaner if I can just get the RV042 to issue a different Default Gateway to DHCP clients. Is this possible?

I don't think you are understanding the request. I want the RV042 to remain the external gatway router. The core swotch is configured to use it as the last hop to the internet for all VLAN's. My simple issue is when using DHCP on the RV042 it gives clients It's own address 192.168.100.1 as the gateway. I want to CHANGE that entry to simply give clients 192168.100.10 as the gateway which is the core switch interface. I don't have a physical DHCP server on the network and I am trying to avoid routing through the RV042 when I have a high speed core routing switch. I just want the RV042 to stay as the last hop gateway and simple change the DHCP gateway entry it's handing out to clients. This really is a simple request and I feel can be done with the telnet console given the right login credentials and the commands to make the change in the DHCP server settings.
This has nothing to do with physical port connectivity, it's a question about the DHCP server configuration in the device, and both WAN ports are already in use for dual WAN connectivity.

Wierd DHCP Issue

Hello All,
I facing a very wierd DHCP issue and would like to know your thoughts on it.
I have my wired clients on vlan 1 and wireless cleints(eap-peap) on VLAN 2.
We are facing an issue where multiple wired clients who were on access port vlan 1 are receiving IP address from wireless subnet(vlan2) -their DHCP server was the WLC virtual gateway IP address(1.1.1.1). This is causing an outage to few wired clients.
The WLC trunk does not have vlan 1 allowed on its ports and all APs are in local mode and all on access vlan.
I'm not entirely sure whats causing this, but only way I think this is possible is that 'A Client' laptop has his network connections bridged - his wired nic on VLAN 1 and wireless NIC on vlan 2, acting like a WGB, which is causing new wired clients(vlan1) DHCP broadcast request forwared through the bidge mode laptop to AP--> WLC. Do you think this is possible??
Havent been able to identify which client is causing this issue yet.
Has anyone faced a similar issue and anyway to block this through WLC/ACS policy?
Thanks
Jino

Hi,
Might we consider to make use of network monitor to take a look at the traffics for the 1.1.1.1 address?
How to use Network Monitor to capture network traffic
Download link here:
Microsoft Network Monitor 3.4
Best regards
Michael Shao
TechNet Community Support

After updating to snow leopard server i can't find DHCP server settings

Hi, where are the DHCP server settings on Lion server, i cant find them anywhere, i need DHCP in my network.
Please help

Have you downloaded Server Admin Tools for Lion Server? (This is different than Server.app).
The link is here.

Very weird dhcp issue

We've started 're-vlanning' our main location here, breaking up depts
into their own vlans.
All seems ok so far, aside from a real doozy.
For the IT vlan, we have one address that will not talk to our web
content mgmt appliance. It's the 2nd address in our assignable pool,
and it doesn't matter if it's dhcp or statically assigned, that address
will not talk to that device.
That is the *only* device that cannot be reached from this particular
address in our dept vlan, every other one works fine.
Any ideas on this?
Stevo

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> and it doesn't matter if it's dhcp or statically assigned, that
> address
So.... the title of this thread should actually be 'Very weird non-DHCP
issue', since your own testing confirms this has nothing to do with DHCP?
If you do a LAN trace on this machine as well as your web content
management appliance do you see packets on either side? Both sides? If
not on both sides but you do on the source (workstation) side see
packets going out, then get LAN traces after each network device
(switch, router, firewall, etc.) to see when the packets disappear.
Feel free to post the LAN traces somewhere with descriptions of IPs,
ports, and what you should be seeing, if you want to post them somewhere
for review.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP4jFPAAoJEF+XTK08PnB55aMP/3Rg9u6LX6jFCXGYuex/oXdS
NZ/liqfCgjyIcykWWeKGgdtm2I7JZOcFiG8YW2le55mcltvCL1VJW +1VGng4kZER
0f4hjfyQ3CcQ6HIU3RM6VL5U2Pblb80MsEQe0qo0xgtPXipmjs i7Q0xIv9p0wT7A
7JMkfgM9tfuI5Yro+BDLfSIkFWicKuKs1sKpNugKalPuyyRrzW IiznoalIKFshon
a40ETLJVZmngBYfqfeZL9nPNsFlveFNXrDkdbl2WbaprsHtNnA NwZfVUIlc5kOCT
MknY0GXof4/tk149OVCCLgjEzoRtTIZH0BJTHQwW7ANkWUUNYwi49+Mk46V0o awl
oe1aA+NK9gl2bWXWLCtTro4ERSVMvkcI0OffytrfcBsqdCKg/g3QPMjV3kiVEULI
xnSTsqFgOl2qO8qGaL6FJtk39ZBnCwqDPtmoNt93OK4hAhWBuA Xihc+kiQHrwkpO
O04quZu8qQG6A6qwFDr+r+QqarFR3kielfvi7H6o5iLfZn/sDhvijGOAknJVctH8
j8fezki9PMznkcT+of2Oe4T99K9fChN2WFSgUKdlpkYSjbkmjP fdbWloou+WBjCm
7hHwnAbKPPgoN8aPPfw9rG9E+K/0YW2kt4wRu79BEDvF6eMv0UdDPE1qPuw1ttmm
jg2zzMZDkgIG39A0P3u7
=+fCy
-----END PGP SIGNATURE-----

6500 DHCP ISSUE

Hello All,
I am having an issue do DHCP from the 6500, and was hoping someone cant help. So, I tried to setup DHCP from the FWSM to the clients and this worked fine with giving out the IP, however the gateway for devices on the inside is supposed to be the 6500, not the FWSM, which is why the clinets wouldn't get out to the internet. Do I need to set up DHCP relay on the FWSM or does anyone know the way I can setup DHCP on the 6500 to give out IP's to the clients. Again just to reiterate, when I setup DHCP on the FWSM the clinets get the IP's but do not get out to the internet and when I setup DHCP on the 6500 the clients do not get an IP. Also I know tghis is a dhcp issue becasue when I assign a static address on the network the clients get out fine. Thanks in advance for the help!
6500 Config
ip dhcp pool TEST
   network 1.1.1.0 255.255.255.0
   default-router 1.1.1.1
   dns-server x.x.x.x y.y.y.y
FWSM Config
FWSM/TEST# show run
interface Vlan3
nameif outside9
bridge-group 1
security-level 0
interface Vlan203
nameif inside9
bridge-group 1
security-level 100
interface BVI1
ip address 1.1.1.4 255.255.255.0
passwd 2KFQnbNIdI.2KYOU encrypted
access-list INSIDE1_IN extended permit ip any any
global (outside1) 1 x.x.x.x
nat (inside1) 1 1.1.1.0 255.255.255.0
access-group INSIDE1_IN in interface inside1
route outside1 0.0.0.0 0.0.0.0 1.1.1.1 1
FWSM/TEST#

Hello Alain,
Thanks for your quick response. I attached a Diagram of the layout. Just to let you know this is an FWSM with many virtual contexts and most including this one that are Transparent. I understand that I need an access-list on both ends to specifiy so the FWSM opens it, I am just having issue because the FWSM sees this as unsual traffic and the access-list needs to be on-point to work. Thank you for the response and I'll look forward to hearing back from you.

VRF and DHCP issue

VRF and DHCP issue
We have a 6500 ( 12.2 (33) SXH5 ) that has a VRF running for our guest network. On this 6500 resides the DHCP pool with a range defined for our guest network. We have a stack of 3750's (12.2 (46) SE) connected to the 6500 with a L3 connection. The 3750's have a local guest VLAN with its gateway defined in a VLAN interface. This VLAN on the 3750 has an IP helper address pointing to an IP within the VRF on the 6500. When debugging DHCP on the 6500, a request is received and sent back out. The client never receives this request.
If a static IP is applied, the client is able to communicate anywhere within the VRF successfully (including pinging the IP within the helper-address. As many posts have pointed out - there is no VRF <name> under the ip dhcp pool <name> within the 6500. I am just wondering if anyone else has run into this and what their solution was.
Thanks.

Hi,
I have tested the dhcp server and vrf on Cisco 3640 and it is working without VRF under the ip dhcp pool. Please ensure that you have configured routing for the dhcp-relay agent(VLAN facing dhcp client on 3750 in your case).

DNS / DHCP Issues in Server 2008R2 Domain

Hi folks,
We’ve been having an ongoing issue for a while now in that some PCs and laptops (Win 7) in our company can’t be contacted by hostname i.e. if we try and RDP from one Windows 7 PC to another the RDP session fails as if the PC isn’t turned on, but it
is indeed turned on and connected to the network.
Even if we ping the host name of a particular computer that is on it fails to reply but if I go into DHCP I can find the hostname bit it has a different IP address assigned to it other than what is listed in DNS for that host name.
So for some reason when some computers get switched on and be allocated a new dynamic IP address through DHCP the corresponding record in DNS doesn’t seem to get updated meaning we need to go into DNS and manually amend the Host A record with the new
IP address that it has been given so we can RDP onto that computer using the hostname.
At present aging and scavenging isn’t enabled in our environment as we are afraid to in case it removes live DNS entries that just haven’t been turned on in a wee while. Does aging and scavenging just ignore static DNS entires and does aging and
scavenging work in DHCP as well?
One other thing I noticed is that if I delete an incorrect DNS Host A record and create it manually and assign the hostname and the correct IP address it says static rather than having a timestamp on it. When I create the new record I always click on our
domain in the Forward Lookup Zone and on creation I always select Create the associated pointer (PTR) record so not sure why the manual record doesn’t get a time stand.
So any help/advice or suggestions would be greatly appreciated.
Thanks,
Bonemister

Hi David,
Thanks for your reply and for clarifying those things for me. Unfortunately in my workplace when I add a manual DNS Host A record it does become a static entry and doesn't have the '0'
you mention, do you have any idea why that would be as I'm worried about it affecting things if I were to enable aging and scavenging.
Is it possible to just enable aging and have it remove entries before a time of my choosing or does scavenging need to be enabled also?
I still can't understand why the relationship between DHCP and DNS isn't working correctly. Sure if DNS has an A record for a computer and the IP address changes via DHCP there is bound to be
a way to setup DNS to be able to update the records it holds - do you know if my reading of this is correct.
By the way, I can confirm that my adapters TCP/IP DNS settings are the same on of the PCs that had the DNS fault as in your screenshot the only different is we have the tick in Append parent suffixes... - would that make a difference.
Thanks also for that other link, it seems very interesting and I'll have a good read through it carefully before doing anything!!
Thanks again for you reply and I look forward to seeing any responses.
Regards,
Bonemister

AP 1140 DHCP Issue

Hi All
I am installing a 3750 switch with integrated controller and 12 x Cisco 1140 AP's. I have configured the 3750 WLC with a management and AP Manager IP address along with 3 WLAN profiles and security settings. I am confident that these are correct, and in any case are, I believe, not related to the problem I have.
None of my AP's would connect to the controller and when I checked the DHCP (Windows Server) server they had not been issued with an IP address. I logged into an AP via the console and saw the following message "Not sending discovery request AP does not have an ip" If I plug a laptop into the port the AP connects to I pick up an IP address without a problem from the DHCP server. This is not a faulty AP issue as none of the AP's are getting an IP address.
The only other relevant fact is that the Windows DHCP server is on a different subnet (VLAN)though I have enabled DHCP forwarding which obviously works as my laptop gets an IP address.
I have raised this with Cisco TAC and their first response has been to get me to configure Option 43. I will try this but am not expecting it to work as the only thing this will do is to return the IP address of the controller. My AP's however are not getting any response.
Any suggestions as to how to resolve would be gratefully received.

Wouldn't option 43 only work when the AP's are actually getting an IP address?
Could you post an extended capture of the AP output during the boot and lack of join?
To make sure you connectivity is what it should be, you could always try manually assigning an IP address to the AP, and also manually tell the AP the controller IP address. If that works, then you likely have a problem with your DHCP server or scope definition. Do you have any MAC assignments/reservations in the DHCP scope? Have you tried reserving the AP IP addresses by MAC address within the relevant DHCP scope?

DHCP issues on wireless

When I connect to my wireless router (D-Link WBR-2310 I believe) using my mac, it gets the default self-assigned address instead of DHCP-assigned address. My PC connects fine wirelessly and wired over ethernet. If the router is reset, it works fine. If I assign manual address to iBook wireless, it works fine (by "works fine" I mean that I can connect to the internet).
Had similar problem with my old Linksys router (Linksys WRT54G) where the following devices had issues connecting to the internet iPod Touch, iBook, PowerBook, and MacBook. This was under unsecured, WEP and WPA settings.It seems that the issue is resurfacing with my current router.
Currently, I am using WPA security (I don't like WEP and neither does my PC). I would rather not switch security settings to unsecured due to the close proximity of my neighbours (yes it's canadian spelling!).
Any suggestions?

I have encountered this same router and issue visiting my future in-laws for the holidays. DHCP with manual address appears to work, but I also still encounter occasional drops. The router is setup for WPA2 security, and support a mix of Mac and Win clients. I haven't put a lot of time into trying to fix it, but here is what I know so far:
1) Sometimes it does just work with DHCP
2) DHCP with manual address works, but will still drop occasionally for brief periods
3) Sometimes, just turning the airport off then on again will resolve the issue and pull an address
4) Just waiting about 30-60 seconds also seems to work -- usually
5) Plugging into the wire works great!
I haven't sat by the router and worked on this, but it seems that occasionally the router just drops the signal, and with it the DHCP assignments. Something about the DHCP implementation is very slow, and it just take a while to get around to assigning an address to my machine. I haven't looked into firmware updates since it's not my box and I don't want to mess it up further and then leave, but that's certainly something to check into.
We also have an 12" PB that cannot even connect to the wireless with the "Error joining wireless network" message. Haven't been able to figure that one out at all.
They may just be getting an Airport or Linksys as a late x-mas gift here... (as my connection drops again while I type this! Airport off, airport on, wait 30 sec, and we're back)
Cheers, and good luck!

Guest Wireless Tunnelling - DHCP Issue

Hi,
I'm attempting to implement Guest Anchor tunnelling between two WLC's but I've run into an odd issue I cannot find a clear answer to.
We have two 5508 WLC's, both Running 7.4.100.0.
The Guest Anchor Controller obviously resides in a DMZ, it's functionality has been proven by connecting an AP directly to it, and connecting the the guest WLAN.
The two controllers have been configured as Mobility Peers, the Mobility Tunnel between them is up (mping and eping both successful, status is up).
The Guest WLAN has been replicated on both controllers, I have set the Mobility Anchor on the WLAN. The Guest Anchor has itself as the mobility anchor and the Internal Controller has the Guest Anchor set.
DHCP is provided by the Guest Anchor's internal DHCP Server. DHCP Proxy is enabled on both Controllers, with the Option 82 format set to AP-MAC. Both Controllers WLAN settings are set to DHCP Server Override, pointed to the Management IP of the Guest Anchor and DHCP Addr. Assignment required.
The problem I'm experiencing is with connecting clients through the Internal WLC. The Client Associates to the Internal WLC and obtains a lease from the Guest Anchor and connects to the network. A few seconds later the client is dessociated from the internal controller. On every subsequent connection attempt, the client does not recieve a response to it's DHCP Requests, and hence ends up with an apipa address.
The Message logs on two controllers return the following errors:
INTERNAL CONTROLLER:
*apfReceiveTask: Jun 27 14:03:25.839: #APF-4-HANDOFF_END_RCVD: apf_mm.c:1626 Handoff end received in wrong role (peer Ip: 0.0.0.0, sender:GUEST_ANCHOR_IP, Role:0) for mobile Client_MAC
GUEST ANCHOR CONTROLLER:
*DHCP Server: Jun 27 14:03:14.466: #DHCP-4-REQIP_NOT_PRESENT: dhcpd.c:559 Received a packet without a requested ip!.
Has anyone else seen similar behaviour? Does anyone have an ideas what might be causing this?
Many Thanks,
Paul

Hi George,
Thanks for the reply.
The Guest WLAN on the Internal Controller is Anchored to the WLC in the DMZ. The Guest Anchor is anchored to itself.
There are only two controllers in the configuration, so breaking off one of the Anchors isn't really an option.
I have tested the Guest Anchor as a Standalone WLC by connecting an AP directly to it, in that configuration DHCP works as expected.

DHCP subnet settings blasted by 10.7.1 server update?

I dutifully applied the 10.7.1 update this evening to my Mini Server (July 2011) and restarted.
Some of the clients on my network were fine but others - those whose DHCP leases expired - had issues getting a new lease. In fact, when these devices were restarted they could not get an IP address at all.
After fiddling around it seems that the subnet which was on previously had been set to off by the reboot. Re-checking the subnet seemed to work but only partially. Some of the subnet settings had been flushed too. Specifically, the router, DNS and search domain settings were reset.
On resetting these settings it all came back to life.
BTW, After much frustration over the past few weeks I have gone with the 192.168.2.xxx set up as proscribed in the k-base article which had been working fine for me until this update.
Looking forward to 10.7.3? I can't imagine all these bugs will be ironed out in the next point release...
Has any one tried using settings other than the settings in the knowledge base article under 10.7.1?

There is a Lion Server Forum where you might be able to get help.
Regards,
Colin R.

WVC200 DHCP issue (LAN vs Wireless

Hi All,
I have a WRT600N router from Linksys and bought a second WVC200 camera.
While setting up the first camera I had some trouble during set up (now I have the same issue with the second one).
During installation of the first camera while on the ethernet hookup as instructed the DHCP assigned a specifc IP (192.168.1.107). After succesfully finishing the initial set up I detached power and the ethernet and hooked up power alone again to switch to a wireless connection.
For whatever reason the router assigned a different IP (192.168.1.115) or so I thought....
After tinkering for a while I upgraded the Firmware to the last version and the wireless conection suddenly worked (the IP did not change).
Now to the second camera.
Did the same thing but somehow after the upgrade the IP still doesn't remain the same (despite DHCP reservation). Still falls back to the 192.168.1.115.
What I realised after checking the router is that the router doesn't recognize the wlan connection for whatever reason. I do WPA TKIP and it works just fine with the other wireless equipment. I also switched off and on the wireless MAC Filter and added the MAC address of the second camera with the right IP (192.168.1.108) in the DHCP reservation list as a device (same in the wireless filter list). I also checked the MAC address at least 10 times....
What else can I do to trick the router in finding the camera and assigning the right IP address or is the wireless connection just broken?
Thx for any help.
Malte
Message Edited by Malte on 08-18-2008 03:14 PM

I have the exact same problem! I have a WVC200 since a couple of years. It have served well but for a while ago it stopped to work properly. I didn't do anything about it right away but today I thought I should set it right.
I did a firmware upgrade, reseted the camera and started all over with the settings. At first I had a TP-cable in it. My router is a Zonet ZSR0140CP that also acts DHCPserver. I have told the DHCP that the MAC-adress of the camera should have a specific IP-adress. In the camera I have set that it should get a IP-adress from DHCP. I have a D-Link DWL-900AP+ that acts wireless AP. It is WEP Encryption with 64 bit HEX. And it doesn't act as a DHCPserver, it's just an AP
Everything went fine until I broke the electricity to the camera unplugged the TP-cable and plugged the elecricity in again.
For a long while it just serched an IP-adress and when it got one it was 192.168.1.115! Thats not much right in that ip adress... Wherever did it got that from??
Please don't tell me to reset everything. I have already done that. And I still have the same problem. I dont think it is the router/switch/AP who is the problem here.
//Camilla

Airport Extreme - possible DHCP issues on UTP ports?

I have a recent (late 2012) iMac which has been consistently connected to my Airport Extreme via UTP with no issues until recently. The Airport Extreme is connected to my single port Motorola 5101 Bigpond Cable Modem.
Connected to the Airport Extreme via UTP are the iMac and a Lacie 4TB NAS media server. There are generally multiple devices connected wirelessly (iPhone, iPad, PS3, XBox) again with no issue.
I have a PC connected to an Airport Express at the other end of the house (PC has no wireless card) and the Express and Extreme are bridged with a common SSID.
Saturday night the "house network" occasionally lost wireless (iPhone switching to 3G) but after resetting the Extreme and the iPhone this seemed to settle down and has been working fine since then (4 days prior to this post).
Later on the Saturday night my iMac lost internet connectivity and resetting the Airport Extreme and resetting the Motorola 5101 did not help. Eventually rebooted the iMac and the Extreme and the 5101 and eventually (after a few minutes) internet connectivity was restored. (Error was "no IP address" and Airport Utility could not see either the Extreme or Express). Connectivity was restored by first turning on WiFi on iMac which immediately got an iP (10.x.x.x) allocated and then after a few minutes the UTP link also came up and remained up when WiFi was turned off.
The iMac has since "lost internet connection" around 3 times in total and a similar process to the above has not always restored connectivity – i.e. doing all the above worked some of the times and did not work others.
When this problem is happening on the iMac UTP connection there are no issues with wireless devices getting an IP allocated.
I am now running the iMac on WiFi with the UTP cable removed. Today I will try a new UTP cable between the iMac and the Airport Extreme to see if there is perhaps some intermittent cable issue.
The Airport Extreme and Airport Express (both a few years old) are running 7.6.4 firmware. I had recently setup timed access for a few wireless devices and also trialled the "guest wireless account" but these were set up around 1 week prior to the recent issues occurring. I have now removed both of these so that the Apple network devices are back to the settings they had which worked fine for years (albeit with different firmware versions over this time).
My diagnosis is that it seems that there is a problem with IPs being allocated by DHCP to devices connected to UTP ports but not over wireless. The only thing that seems to contradict this is that the Lacie NAS drive which is UTP connected (to UTP port 3) seems to still work and be accessible without issue.
So am also wondering if there is some intermittent iMac issue with the UTP port or with the cable. Will change the cable today as mentioned above to confirm or otherwise.
Any advice on further diagnostic processes and/or thoughts on Airport Extreme issues (hardware or firmware) etc would be appreciated. A search of the forums did not show anything similar but my search was not super-extensive.
Thank you for any help anyone can provide.
Andrew

In the end after LOTS of troubleshooting and testing - and WAY too much frustration Apple - this issue has proved to simply be what I assume is a bug in the Automatic network location management under Mavericks and I had this issue to a lesser degree with 10.8.5.
I have now setup a "Home" new network location and my connection has been 150% stable ever since.
So nice to not need to reboot my Mac 7 times a day or more after several weeks of significant frustration.

E4200 - DHCP issues

Latest E4200 firmware has a bug in DHCPd. Manifests itself if the IP is reserved, system is dual boot w different hostnames

I'd accept if the both OSes get different IP addresses. Issue is a bit worse than that.
Below is the formal definition of the problem in long format. Hope that it brings everything to light:
To Forsaken
The hostname in the table is StormOne, which is the same hostname of my Linux. I just used "add selected hosts" from the table, nothing added manually.
Problem
DHCPd confuses and cannot provide IP address to a MAC if different hostnames are presented throught that MAC and that MAC has a reserved IP.
Preliminary Definitions & Information
Experience of the poster: Linux cluster administrator (~300 nodes) and developer.
Most used OS: Debian Linux (Testing branch)
Alternate OS: Windows 7 Ultimate
Steps to Reproduce
Boot to your most used OS on your PC.
After complete boot, login to the router.
From basic setup -> DHCP reservation, reserve your IP and save the settings.
Logout.
Boot to your alternate OS.
Get a new IP from unreserved block.
Use it for sometime.
Reboot to your most used OS again.
Wait for network to come up.
You'll get a DHCP timeout because you have two hostnames and IPs point to same MAC and DHCPd confuses which IP to give.
What Should Happen
Boot to your most used OS on your PC.
After complete boot, login to the router.
From basic setup -> DHCP reservation, reserve your IP and save the settings.
Logout.
Boot to your alternate OS.
Network comes up with your reserved IP and the hostname on the router (hostname part is a design decision but it should override the windows' hostname since it's the specification)
Reboot to your most used OS again
Your network comes up with the same, reserved IP and everything is fine and dandy.
How to Solve the Problem
Do one of the following:
Log in to your router with an alternate device and delete the reservation and down/up the network from the OS.
Use same hostnames on the OSes (Didn't try it yet)
Use your alternate OS to delete the lease.
Why It Happens
For an unknown reason, the new firmware tries to match hosts using both Hostname and MAC. That shouldn't happen IMHO. MAC is sufficient. If Hostname and MAC should be checked both, DHCPd shouldn't fumble and fall but give the correct IP according to hostname (and if it worked that way it'd be kinda cool TBH).

Dhcp issues / settings

Similar Messages

Maybe you are looking for