Windows Server 2008 DHCP: Lease offered, but not acceptedWindows 2008 R2 DHCP server not responding to DHCP discoverWhy would Windows Server not respond to DHCP DISCOVER?DHCP server identifier and DHCP relayMultiple Homed Windows 2008 Server / Windows 7 ClientWindows Server 2008 DHCP with RRASClient not getting address from some DHCP serverIncorrect lease times from Windows 2012 R2 DHCPPolycom phone not requesting DHCP offerWhy does a DHCP4 client not respond to the DHCP Offer from a DHCP server?DHCP snooping prevents client server from receiving IP
In general, would I need to season a meat when making a sauce?
Is real public IP Address hidden when using a system wide proxy in Windows 10?
Why is this Simple Puzzle impossible to solve?
Can a person survive on blood in place of water?
Is the Indo-European language family made up?
Who will lead the country until there is a new Tory leader?
What is a Centaur Thief's climbing speed?
How should I introduce map drawing to my players?
Why does Mjolnir fall down in Age of Ultron but not in Endgame?
Why do most published works in medical imaging try to reduce false positives?
Popcorn is the only acceptable snack to consume while watching a movie
Can I tell a prospective employee that everyone in the team is leaving?
I know that there is a preselected candidate for a position to be filled at my department. What should I do?
Any advice on creating fictional locations in real places when writing historical fiction?
Did 20% of US soldiers in Vietnam use heroin, 95% of whom quit afterwards?
Inclusion of standard error in regression equation
Is it rude to call a professor by their last name with no prefix in a non-academic setting?
What does this symbol on the box of power supply mean?
How strong are Wi-Fi signals?
What to do when you've set the wrong ISO for your film?
Alignment: "Breaking out" of environment (enumerate / minipage)
Could a 19.25mm revolver actually exist?
Is DateWithin30Days(Date 1, Date 2) an Apex Method?
Plot twist where the antagonist wins
Windows Server 2008 DHCP: Lease offered, but not accepted
Windows 2008 R2 DHCP server not responding to DHCP discoverWhy would Windows Server not respond to DHCP DISCOVER?DHCP server identifier and DHCP relayMultiple Homed Windows 2008 Server / Windows 7 ClientWindows Server 2008 DHCP with RRASClient not getting address from some DHCP serverIncorrect lease times from Windows 2012 R2 DHCPPolycom phone not requesting DHCP offerWhy does a DHCP4 client not respond to the DHCP Offer from a DHCP server?DHCP snooping prevents client server from receiving IP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
My Windows Server 2008 should be configured to work as a DHCP Server in the Network.
Therefore I setup the Role and configured everything.
I have downloaded a tiny tool, that can show DHCP-Offers on the Network. When executing it, i receive:
Packet from 192.168.100.5
Offered IP 192.168.100.202
Subnet Mask 255.255.255.0
Renew Due in 345600 Seconds
Lease Length 691200 Seconds
-------------------------
So this seems to work fine. However if I setup my network card to receive an IP from DHCP, it simple does not receive anything. Windows (Client) then picks up its default "No-DHCP-Available" Adress like "169.254.21.222 (Preferred)"
Service is Running, IPs are "offered", Also Login-Data for Dynamic DNS Update (DHCP == DC) is configured.
Windows Server Logs show nothing. Any Idea how I could debug this best?
edit: The DHCP is authorized on the Domain as well.
UPDATE 1: Wireshark:
I downloaded Wireshark for the Server and for the Client. Started it, and tried to /release, /renew IP-Adress... Nothing was logged (used filter (bootp.option.type == 53)) - Neither on Server, nor on Client side.
So, I disabled DHCP on my Server, re-enabled it on my dedicated router (Fritz Box), rebooted the client, and finally could trace a request done by the client:
8328 7.052393000 192.168.100.29 192.168.100.2 DHCP 362 DHCP Request - Transaction ID 0x51a0cafa
8329 7.054365000 192.168.100.2 192.168.100.29 DHCP 590 DHCP ACK - Transaction ID 0x51a0cafa
So, the client seems to work well in terms of DHCP.
I Enabled DHCP on the Server again, and set up the client to use a dynamic IP, but using the DNS of my Server as the primary (and only) DNS-Server. Again, I get nothing. (And again no Wireshark Logs on any device)
I noticed, that when doing /release, /renew, the /renew always throws an error, when having the DHCP on the Server enabled. (An attempt was made to access a socket in a way forbidden by its access permissions.)
But this looks like a local error to me, not sure what it has to do with the presence (or absence) of any DHCP Server.
UPDATE 2: I now did the following: Using a Static IP Adress, I started Wireshark on the Server, and switched to a Automatic Configuration on the Client. It didn't receive a IP-Adress (using the default of 169.254.21.222. Again, no Wireshark logs on the server.
Then I used the same configuration, and used the DHCP-Finder-Tool. Now the Server logged several DHCP Discovery Entries from THAT IP-Adress.
779 55.354991000 169.254.21.222 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x9a020000
780 55.355668000 192.168.100.5 255.255.255.255 DHCP 342 DHCP Offer - Transaction ID 0x9a020000
However the client did NOT receive a IP Adress. Also the tool did not show any response, as it does, when using it from a hardcoded IP-Adress from within the same subnet.
UPDATE 3: Now I am Confused: Just checked the Adressleases of the DHCP and noted, that ANY WLAN-Device out there has successfully leased an IP Adress. (Duration ~ 8days)
However, for my (wired) Clients it still fails... ?
https://abload.de/img/wifi1b3xf7.png
Wlan Clients are connected through an AccessPoint, that is connected to the very same 24-port switch every wired client is...
Just connected my PC with a spare WLAN-USB-Dongle - Worked perfectly fine...
https://abload.de/img/wifi23ojcg.png
ps.: I am very very familar with server setups - but this blows my mind - Why would there be a distinction between WLAN and WIRED clients, when it comes down to DHCP ?!
After Rebooting (and multiple times en/disabling) the client('s network connection) it works...
Maybe there is a "Cache" layer, that delayes the access on "new" DHCP Servers... However, so far my local client is the only one out of 20 that has successfully requested an ip-adress... i'll leave it like that and check the status tomorrow.
windows-server-2008 dhcp
edited Mar 8 '17 at 18:01
Community♦
1
asked Mar 19 '14 at 20:07
dognosedognose
1307
|
show 2 more comments
My Windows Server 2008 should be configured to work as a DHCP Server in the Network.
Therefore I setup the Role and configured everything.
I have downloaded a tiny tool, that can show DHCP-Offers on the Network. When executing it, i receive:
Packet from 192.168.100.5
Offered IP 192.168.100.202
Subnet Mask 255.255.255.0
Renew Due in 345600 Seconds
Lease Length 691200 Seconds
-------------------------
So this seems to work fine. However if I setup my network card to receive an IP from DHCP, it simple does not receive anything. Windows (Client) then picks up its default "No-DHCP-Available" Adress like "169.254.21.222 (Preferred)"
Service is Running, IPs are "offered", Also Login-Data for Dynamic DNS Update (DHCP == DC) is configured.
Windows Server Logs show nothing. Any Idea how I could debug this best?
edit: The DHCP is authorized on the Domain as well.
UPDATE 1: Wireshark:
I downloaded Wireshark for the Server and for the Client. Started it, and tried to /release, /renew IP-Adress... Nothing was logged (used filter (bootp.option.type == 53)) - Neither on Server, nor on Client side.
So, I disabled DHCP on my Server, re-enabled it on my dedicated router (Fritz Box), rebooted the client, and finally could trace a request done by the client:
8328 7.052393000 192.168.100.29 192.168.100.2 DHCP 362 DHCP Request - Transaction ID 0x51a0cafa
8329 7.054365000 192.168.100.2 192.168.100.29 DHCP 590 DHCP ACK - Transaction ID 0x51a0cafa
So, the client seems to work well in terms of DHCP.
I Enabled DHCP on the Server again, and set up the client to use a dynamic IP, but using the DNS of my Server as the primary (and only) DNS-Server. Again, I get nothing. (And again no Wireshark Logs on any device)
I noticed, that when doing /release, /renew, the /renew always throws an error, when having the DHCP on the Server enabled. (An attempt was made to access a socket in a way forbidden by its access permissions.)
But this looks like a local error to me, not sure what it has to do with the presence (or absence) of any DHCP Server.
UPDATE 2: I now did the following: Using a Static IP Adress, I started Wireshark on the Server, and switched to a Automatic Configuration on the Client. It didn't receive a IP-Adress (using the default of 169.254.21.222. Again, no Wireshark logs on the server.
Then I used the same configuration, and used the DHCP-Finder-Tool. Now the Server logged several DHCP Discovery Entries from THAT IP-Adress.
779 55.354991000 169.254.21.222 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x9a020000
780 55.355668000 192.168.100.5 255.255.255.255 DHCP 342 DHCP Offer - Transaction ID 0x9a020000
However the client did NOT receive a IP Adress. Also the tool did not show any response, as it does, when using it from a hardcoded IP-Adress from within the same subnet.
UPDATE 3: Now I am Confused: Just checked the Adressleases of the DHCP and noted, that ANY WLAN-Device out there has successfully leased an IP Adress. (Duration ~ 8days)
However, for my (wired) Clients it still fails... ?
https://abload.de/img/wifi1b3xf7.png
Wlan Clients are connected through an AccessPoint, that is connected to the very same 24-port switch every wired client is...
Just connected my PC with a spare WLAN-USB-Dongle - Worked perfectly fine...
https://abload.de/img/wifi23ojcg.png
ps.: I am very very familar with server setups - but this blows my mind - Why would there be a distinction between WLAN and WIRED clients, when it comes down to DHCP ?!
After Rebooting (and multiple times en/disabling) the client('s network connection) it works...
Maybe there is a "Cache" layer, that delayes the access on "new" DHCP Servers... However, so far my local client is the only one out of 20 that has successfully requested an ip-adress... i'll leave it like that and check the status tomorrow.
windows-server-2008 dhcp
edited Mar 8 '17 at 18:01
Community♦
1
asked Mar 19 '14 at 20:07
dognosedognose
1307
1
Are the client machine and the DHCP server connected to the same physical segment?
– joeqwerty
Mar 19 '14 at 20:19
@joeqwerty I would Assume Yes. Line Up looks likePC <-> 8 port switch <-> 24 port switch <-> DHCP-Server(Server and 24 port are in the rack, 8 port is in this room. Physical connection is fine, when using a static ip adress on the client)
– dognose
Mar 19 '14 at 20:44
1
OK, here's what I would do: run a packet capture program (like Wireshark) on the server and the client and start a simultaneous capture. Then runipconfig/releaseandipconfig/renewon the client and look at the capture on both sides to get some idea of what's happening. You can filter the capture to show only DHCP related traffic and you should see the DORA process from both sides.
– joeqwerty
Mar 19 '14 at 20:47
Trying running wireshark from the client to see if you can see arp requests, its possible that your network is some how blocking it.
– the dave
Mar 19 '14 at 21:06
1
Check your switches, especially if they are manageable, and look for dhcp/bootp relay/forwarding settings and make sure they are set to go to the Windows server.
– TheCleaner
Mar 19 '14 at 21:45
|
show 2 more comments
My Windows Server 2008 should be configured to work as a DHCP Server in the Network.
Therefore I setup the Role and configured everything.
I have downloaded a tiny tool, that can show DHCP-Offers on the Network. When executing it, i receive:
Packet from 192.168.100.5
Offered IP 192.168.100.202
Subnet Mask 255.255.255.0
Renew Due in 345600 Seconds
Lease Length 691200 Seconds
-------------------------
So this seems to work fine. However if I setup my network card to receive an IP from DHCP, it simple does not receive anything. Windows (Client) then picks up its default "No-DHCP-Available" Adress like "169.254.21.222 (Preferred)"
Service is Running, IPs are "offered", Also Login-Data for Dynamic DNS Update (DHCP == DC) is configured.
Windows Server Logs show nothing. Any Idea how I could debug this best?
edit: The DHCP is authorized on the Domain as well.
UPDATE 1: Wireshark:
I downloaded Wireshark for the Server and for the Client. Started it, and tried to /release, /renew IP-Adress... Nothing was logged (used filter (bootp.option.type == 53)) - Neither on Server, nor on Client side.
So, I disabled DHCP on my Server, re-enabled it on my dedicated router (Fritz Box), rebooted the client, and finally could trace a request done by the client:
8328 7.052393000 192.168.100.29 192.168.100.2 DHCP 362 DHCP Request - Transaction ID 0x51a0cafa
8329 7.054365000 192.168.100.2 192.168.100.29 DHCP 590 DHCP ACK - Transaction ID 0x51a0cafa
So, the client seems to work well in terms of DHCP.
I Enabled DHCP on the Server again, and set up the client to use a dynamic IP, but using the DNS of my Server as the primary (and only) DNS-Server. Again, I get nothing. (And again no Wireshark Logs on any device)
I noticed, that when doing /release, /renew, the /renew always throws an error, when having the DHCP on the Server enabled. (An attempt was made to access a socket in a way forbidden by its access permissions.)
But this looks like a local error to me, not sure what it has to do with the presence (or absence) of any DHCP Server.
UPDATE 2: I now did the following: Using a Static IP Adress, I started Wireshark on the Server, and switched to a Automatic Configuration on the Client. It didn't receive a IP-Adress (using the default of 169.254.21.222. Again, no Wireshark logs on the server.
Then I used the same configuration, and used the DHCP-Finder-Tool. Now the Server logged several DHCP Discovery Entries from THAT IP-Adress.
779 55.354991000 169.254.21.222 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x9a020000
780 55.355668000 192.168.100.5 255.255.255.255 DHCP 342 DHCP Offer - Transaction ID 0x9a020000
However the client did NOT receive a IP Adress. Also the tool did not show any response, as it does, when using it from a hardcoded IP-Adress from within the same subnet.
UPDATE 3: Now I am Confused: Just checked the Adressleases of the DHCP and noted, that ANY WLAN-Device out there has successfully leased an IP Adress. (Duration ~ 8days)
However, for my (wired) Clients it still fails... ?
https://abload.de/img/wifi1b3xf7.png
Wlan Clients are connected through an AccessPoint, that is connected to the very same 24-port switch every wired client is...
Just connected my PC with a spare WLAN-USB-Dongle - Worked perfectly fine...
https://abload.de/img/wifi23ojcg.png
ps.: I am very very familar with server setups - but this blows my mind - Why would there be a distinction between WLAN and WIRED clients, when it comes down to DHCP ?!
After Rebooting (and multiple times en/disabling) the client('s network connection) it works...
Maybe there is a "Cache" layer, that delayes the access on "new" DHCP Servers... However, so far my local client is the only one out of 20 that has successfully requested an ip-adress... i'll leave it like that and check the status tomorrow.
windows-server-2008 dhcp
edited Mar 8 '17 at 18:01
Community♦
1
asked Mar 19 '14 at 20:07
dognosedognose
1307
My Windows Server 2008 should be configured to work as a DHCP Server in the Network.
Therefore I setup the Role and configured everything.
I have downloaded a tiny tool, that can show DHCP-Offers on the Network. When executing it, i receive:
Packet from 192.168.100.5
Offered IP 192.168.100.202
Subnet Mask 255.255.255.0
Renew Due in 345600 Seconds
Lease Length 691200 Seconds
-------------------------
So this seems to work fine. However if I setup my network card to receive an IP from DHCP, it simple does not receive anything. Windows (Client) then picks up its default "No-DHCP-Available" Adress like "169.254.21.222 (Preferred)"
Service is Running, IPs are "offered", Also Login-Data for Dynamic DNS Update (DHCP == DC) is configured.
Windows Server Logs show nothing. Any Idea how I could debug this best?
edit: The DHCP is authorized on the Domain as well.
UPDATE 1: Wireshark:
I downloaded Wireshark for the Server and for the Client. Started it, and tried to /release, /renew IP-Adress... Nothing was logged (used filter (bootp.option.type == 53)) - Neither on Server, nor on Client side.
So, I disabled DHCP on my Server, re-enabled it on my dedicated router (Fritz Box), rebooted the client, and finally could trace a request done by the client:
8328 7.052393000 192.168.100.29 192.168.100.2 DHCP 362 DHCP Request - Transaction ID 0x51a0cafa
8329 7.054365000 192.168.100.2 192.168.100.29 DHCP 590 DHCP ACK - Transaction ID 0x51a0cafa
So, the client seems to work well in terms of DHCP.
I Enabled DHCP on the Server again, and set up the client to use a dynamic IP, but using the DNS of my Server as the primary (and only) DNS-Server. Again, I get nothing. (And again no Wireshark Logs on any device)
I noticed, that when doing /release, /renew, the /renew always throws an error, when having the DHCP on the Server enabled. (An attempt was made to access a socket in a way forbidden by its access permissions.)
But this looks like a local error to me, not sure what it has to do with the presence (or absence) of any DHCP Server.
UPDATE 2: I now did the following: Using a Static IP Adress, I started Wireshark on the Server, and switched to a Automatic Configuration on the Client. It didn't receive a IP-Adress (using the default of 169.254.21.222. Again, no Wireshark logs on the server.
Then I used the same configuration, and used the DHCP-Finder-Tool. Now the Server logged several DHCP Discovery Entries from THAT IP-Adress.
779 55.354991000 169.254.21.222 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x9a020000
780 55.355668000 192.168.100.5 255.255.255.255 DHCP 342 DHCP Offer - Transaction ID 0x9a020000
However the client did NOT receive a IP Adress. Also the tool did not show any response, as it does, when using it from a hardcoded IP-Adress from within the same subnet.
UPDATE 3: Now I am Confused: Just checked the Adressleases of the DHCP and noted, that ANY WLAN-Device out there has successfully leased an IP Adress. (Duration ~ 8days)
However, for my (wired) Clients it still fails... ?
https://abload.de/img/wifi1b3xf7.png
Wlan Clients are connected through an AccessPoint, that is connected to the very same 24-port switch every wired client is...
Just connected my PC with a spare WLAN-USB-Dongle - Worked perfectly fine...
https://abload.de/img/wifi23ojcg.png
ps.: I am very very familar with server setups - but this blows my mind - Why would there be a distinction between WLAN and WIRED clients, when it comes down to DHCP ?!
After Rebooting (and multiple times en/disabling) the client('s network connection) it works...
Maybe there is a "Cache" layer, that delayes the access on "new" DHCP Servers... However, so far my local client is the only one out of 20 that has successfully requested an ip-adress... i'll leave it like that and check the status tomorrow.
windows-server-2008 dhcp
windows-server-2008 dhcp
edited Mar 8 '17 at 18:01
Community♦
1
asked Mar 19 '14 at 20:07
dognosedognose
1307
edited Mar 8 '17 at 18:01
Community♦
1
asked Mar 19 '14 at 20:07
dognosedognose
1307
edited Mar 8 '17 at 18:01
Community♦
1
edited Mar 8 '17 at 18:01
Community♦
1
edited Mar 8 '17 at 18:01
Community♦
1
1
asked Mar 19 '14 at 20:07
dognosedognose
1307
asked Mar 19 '14 at 20:07
dognosedognose
1307
asked Mar 19 '14 at 20:07
dognosedognose
1307
1307
1
Are the client machine and the DHCP server connected to the same physical segment?
– joeqwerty
Mar 19 '14 at 20:19
@joeqwerty I would Assume Yes. Line Up looks likePC <-> 8 port switch <-> 24 port switch <-> DHCP-Server(Server and 24 port are in the rack, 8 port is in this room. Physical connection is fine, when using a static ip adress on the client)
– dognose
Mar 19 '14 at 20:44
1
OK, here's what I would do: run a packet capture program (like Wireshark) on the server and the client and start a simultaneous capture. Then runipconfig/releaseandipconfig/renewon the client and look at the capture on both sides to get some idea of what's happening. You can filter the capture to show only DHCP related traffic and you should see the DORA process from both sides.
– joeqwerty
Mar 19 '14 at 20:47
Trying running wireshark from the client to see if you can see arp requests, its possible that your network is some how blocking it.
– the dave
Mar 19 '14 at 21:06
1
Check your switches, especially if they are manageable, and look for dhcp/bootp relay/forwarding settings and make sure they are set to go to the Windows server.
– TheCleaner
Mar 19 '14 at 21:45
|
show 2 more comments
1
Are the client machine and the DHCP server connected to the same physical segment?
– joeqwerty
Mar 19 '14 at 20:19
@joeqwerty I would Assume Yes. Line Up looks likePC <-> 8 port switch <-> 24 port switch <-> DHCP-Server(Server and 24 port are in the rack, 8 port is in this room. Physical connection is fine, when using a static ip adress on the client)
– dognose
Mar 19 '14 at 20:44
1
OK, here's what I would do: run a packet capture program (like Wireshark) on the server and the client and start a simultaneous capture. Then runipconfig/releaseandipconfig/renewon the client and look at the capture on both sides to get some idea of what's happening. You can filter the capture to show only DHCP related traffic and you should see the DORA process from both sides.
– joeqwerty
Mar 19 '14 at 20:47
Trying running wireshark from the client to see if you can see arp requests, its possible that your network is some how blocking it.
– the dave
Mar 19 '14 at 21:06
1
Check your switches, especially if they are manageable, and look for dhcp/bootp relay/forwarding settings and make sure they are set to go to the Windows server.
– TheCleaner
Mar 19 '14 at 21:45
1
1
Are the client machine and the DHCP server connected to the same physical segment?
– joeqwerty
Mar 19 '14 at 20:19
Are the client machine and the DHCP server connected to the same physical segment?
– joeqwerty
Mar 19 '14 at 20:19
@joeqwerty I would Assume Yes. Line Up looks like
PC <-> 8 port switch <-> 24 port switch <-> DHCP-Server (Server and 24 port are in the rack, 8 port is in this room. Physical connection is fine, when using a static ip adress on the client)– dognose
Mar 19 '14 at 20:44
@joeqwerty I would Assume Yes. Line Up looks like
PC <-> 8 port switch <-> 24 port switch <-> DHCP-Server (Server and 24 port are in the rack, 8 port is in this room. Physical connection is fine, when using a static ip adress on the client)– dognose
Mar 19 '14 at 20:44
1
1
OK, here's what I would do: run a packet capture program (like Wireshark) on the server and the client and start a simultaneous capture. Then run
ipconfig/release and ipconfig/renew on the client and look at the capture on both sides to get some idea of what's happening. You can filter the capture to show only DHCP related traffic and you should see the DORA process from both sides.– joeqwerty
Mar 19 '14 at 20:47
OK, here's what I would do: run a packet capture program (like Wireshark) on the server and the client and start a simultaneous capture. Then run
ipconfig/release and ipconfig/renew on the client and look at the capture on both sides to get some idea of what's happening. You can filter the capture to show only DHCP related traffic and you should see the DORA process from both sides.– joeqwerty
Mar 19 '14 at 20:47
Trying running wireshark from the client to see if you can see arp requests, its possible that your network is some how blocking it.
– the dave
Mar 19 '14 at 21:06
Trying running wireshark from the client to see if you can see arp requests, its possible that your network is some how blocking it.
– the dave
Mar 19 '14 at 21:06
1
1
Check your switches, especially if they are manageable, and look for dhcp/bootp relay/forwarding settings and make sure they are set to go to the Windows server.
– TheCleaner
Mar 19 '14 at 21:45
Check your switches, especially if they are manageable, and look for dhcp/bootp relay/forwarding settings and make sure they are set to go to the Windows server.
– TheCleaner
Mar 19 '14 at 21:45
|
show 2 more comments
1 Answer
1
active
oldest
votes
It sounds like you need to setup a DHCP relay or a helper IP address on your managed switch that points to the DHCP server.
You might also have an issue with the physical wiring on that segment. Most routers can provide DHCP across the LAN ports and pass traffic up the WAN port. If DHCP is disabled, routers work like switches across their LAN ports. The 24 port switch should be moved off the WAN port onto a LAN port.
I'm not exactly sure of the specific models of switches/routers in your network or how they are designed so this might not apply to your specific situation.
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f583237%2fwindows-server-2008-dhcp-lease-offered-but-not-accepted%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It sounds like you need to setup a DHCP relay or a helper IP address on your managed switch that points to the DHCP server.
You might also have an issue with the physical wiring on that segment. Most routers can provide DHCP across the LAN ports and pass traffic up the WAN port. If DHCP is disabled, routers work like switches across their LAN ports. The 24 port switch should be moved off the WAN port onto a LAN port.
I'm not exactly sure of the specific models of switches/routers in your network or how they are designed so this might not apply to your specific situation.
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
add a comment |
It sounds like you need to setup a DHCP relay or a helper IP address on your managed switch that points to the DHCP server.
You might also have an issue with the physical wiring on that segment. Most routers can provide DHCP across the LAN ports and pass traffic up the WAN port. If DHCP is disabled, routers work like switches across their LAN ports. The 24 port switch should be moved off the WAN port onto a LAN port.
I'm not exactly sure of the specific models of switches/routers in your network or how they are designed so this might not apply to your specific situation.
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
add a comment |
It sounds like you need to setup a DHCP relay or a helper IP address on your managed switch that points to the DHCP server.
You might also have an issue with the physical wiring on that segment. Most routers can provide DHCP across the LAN ports and pass traffic up the WAN port. If DHCP is disabled, routers work like switches across their LAN ports. The 24 port switch should be moved off the WAN port onto a LAN port.
I'm not exactly sure of the specific models of switches/routers in your network or how they are designed so this might not apply to your specific situation.
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
It sounds like you need to setup a DHCP relay or a helper IP address on your managed switch that points to the DHCP server.
You might also have an issue with the physical wiring on that segment. Most routers can provide DHCP across the LAN ports and pass traffic up the WAN port. If DHCP is disabled, routers work like switches across their LAN ports. The 24 port switch should be moved off the WAN port onto a LAN port.
I'm not exactly sure of the specific models of switches/routers in your network or how they are designed so this might not apply to your specific situation.
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
answered Mar 19 '14 at 23:49
Byron C.Byron C.
5971615
5971615
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f583237%2fwindows-server-2008-dhcp-lease-offered-but-not-accepted%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Are the client machine and the DHCP server connected to the same physical segment?
– joeqwerty
Mar 19 '14 at 20:19
@joeqwerty I would Assume Yes. Line Up looks like
PC <-> 8 port switch <-> 24 port switch <-> DHCP-Server(Server and 24 port are in the rack, 8 port is in this room. Physical connection is fine, when using a static ip adress on the client)– dognose
Mar 19 '14 at 20:44
1
OK, here's what I would do: run a packet capture program (like Wireshark) on the server and the client and start a simultaneous capture. Then run
ipconfig/releaseandipconfig/renewon the client and look at the capture on both sides to get some idea of what's happening. You can filter the capture to show only DHCP related traffic and you should see the DORA process from both sides.– joeqwerty
Mar 19 '14 at 20:47
Trying running wireshark from the client to see if you can see arp requests, its possible that your network is some how blocking it.
– the dave
Mar 19 '14 at 21:06
1
Check your switches, especially if they are manageable, and look for dhcp/bootp relay/forwarding settings and make sure they are set to go to the Windows server.
– TheCleaner
Mar 19 '14 at 21:45