Windows DHCP issue BAD_ADDRESS
This is interesting. we have several MS Surface's with MS docks and we are connecting then via Ethernet.
We are noticing that these Surface's when connecting through dock are causing BAD_ADDRESS in the DHCP and thus making all available IPs unusable. So we have to manually clear them. This does not happen with WiFi or any other computers.
I have updated the firmware of the MS docks to the latest and still having this issue.
The DHCP Log states:
2,01/29/19,08:19:22,DNS Update Successful,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
30,01/29/19,08:21:14,DNS Update Request,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
11,01/29/19,08:21:14,Renew,10.10.0.231,Surface3-001.XYZ.com,B831B52E457F,,2769639364,0,,,,0x4D53465420352E30,MSFT 5.0,,,,0
This is repeated for all BAD_ADDRESS.
We have assigned static IP (10.10.0.231) to this particular Surface but it is still doing this.
DHCP and DNS is on primary DC on MS 2012-R2 server.
2nd DNS is on backup DC.
Any ideas?
Edit:
To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. In the DHCP logs I see the entries mentioned above related to all the BAD_ADDRESSES.
We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
windows dhcp microsoft-surface
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
add a comment |
This is interesting. we have several MS Surface's with MS docks and we are connecting then via Ethernet.
We are noticing that these Surface's when connecting through dock are causing BAD_ADDRESS in the DHCP and thus making all available IPs unusable. So we have to manually clear them. This does not happen with WiFi or any other computers.
I have updated the firmware of the MS docks to the latest and still having this issue.
The DHCP Log states:
2,01/29/19,08:19:22,DNS Update Successful,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
30,01/29/19,08:21:14,DNS Update Request,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
11,01/29/19,08:21:14,Renew,10.10.0.231,Surface3-001.XYZ.com,B831B52E457F,,2769639364,0,,,,0x4D53465420352E30,MSFT 5.0,,,,0
This is repeated for all BAD_ADDRESS.
We have assigned static IP (10.10.0.231) to this particular Surface but it is still doing this.
DHCP and DNS is on primary DC on MS 2012-R2 server.
2nd DNS is on backup DC.
Any ideas?
Edit:
To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. In the DHCP logs I see the entries mentioned above related to all the BAD_ADDRESSES.
We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
windows dhcp microsoft-surface
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
For other Surfaces we have put them on wifi to avoid this. but would like to use the Ethernet on the dock as wifi signals in the building are too many and cause interference.
– Sid_Hussey
Jan 29 at 17:15
So where exactly are you seeing theBAD_ADDRESSerror? Please edit the question to clarify this.
– DavidPostill♦
Jan 29 at 21:36
Hi DavidPostil, Thanks for replying, I did mention it is in the DHCP server. To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
– Sid_Hussey
Jan 30 at 15:15
add a comment |
This is interesting. we have several MS Surface's with MS docks and we are connecting then via Ethernet.
We are noticing that these Surface's when connecting through dock are causing BAD_ADDRESS in the DHCP and thus making all available IPs unusable. So we have to manually clear them. This does not happen with WiFi or any other computers.
I have updated the firmware of the MS docks to the latest and still having this issue.
The DHCP Log states:
2,01/29/19,08:19:22,DNS Update Successful,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
30,01/29/19,08:21:14,DNS Update Request,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
11,01/29/19,08:21:14,Renew,10.10.0.231,Surface3-001.XYZ.com,B831B52E457F,,2769639364,0,,,,0x4D53465420352E30,MSFT 5.0,,,,0
This is repeated for all BAD_ADDRESS.
We have assigned static IP (10.10.0.231) to this particular Surface but it is still doing this.
DHCP and DNS is on primary DC on MS 2012-R2 server.
2nd DNS is on backup DC.
Any ideas?
Edit:
To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. In the DHCP logs I see the entries mentioned above related to all the BAD_ADDRESSES.
We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
windows dhcp microsoft-surface
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
This is interesting. we have several MS Surface's with MS docks and we are connecting then via Ethernet.
We are noticing that these Surface's when connecting through dock are causing BAD_ADDRESS in the DHCP and thus making all available IPs unusable. So we have to manually clear them. This does not happen with WiFi or any other computers.
I have updated the firmware of the MS docks to the latest and still having this issue.
The DHCP Log states:
2,01/29/19,08:19:22,DNS Update Successful,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
30,01/29/19,08:21:14,DNS Update Request,10.10.0.231,Surface3-001.XYZ.com,,,0,6,,,,,,,,,0
11,01/29/19,08:21:14,Renew,10.10.0.231,Surface3-001.XYZ.com,B831B52E457F,,2769639364,0,,,,0x4D53465420352E30,MSFT 5.0,,,,0
This is repeated for all BAD_ADDRESS.
We have assigned static IP (10.10.0.231) to this particular Surface but it is still doing this.
DHCP and DNS is on primary DC on MS 2012-R2 server.
2nd DNS is on backup DC.
Any ideas?
Edit:
To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. In the DHCP logs I see the entries mentioned above related to all the BAD_ADDRESSES.
We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
windows dhcp microsoft-surface
windows dhcp microsoft-surface
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
edited Jan 30 at 15:20
Sid_Hussey
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
asked Jan 29 at 17:14
Sid_HusseySid_Hussey
617
617
For other Surfaces we have put them on wifi to avoid this. but would like to use the Ethernet on the dock as wifi signals in the building are too many and cause interference.
– Sid_Hussey
Jan 29 at 17:15
So where exactly are you seeing theBAD_ADDRESSerror? Please edit the question to clarify this.
– DavidPostill♦
Jan 29 at 21:36
Hi DavidPostil, Thanks for replying, I did mention it is in the DHCP server. To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
– Sid_Hussey
Jan 30 at 15:15
add a comment |
For other Surfaces we have put them on wifi to avoid this. but would like to use the Ethernet on the dock as wifi signals in the building are too many and cause interference.
– Sid_Hussey
Jan 29 at 17:15
So where exactly are you seeing theBAD_ADDRESSerror? Please edit the question to clarify this.
– DavidPostill♦
Jan 29 at 21:36
Hi DavidPostil, Thanks for replying, I did mention it is in the DHCP server. To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
– Sid_Hussey
Jan 30 at 15:15
For other Surfaces we have put them on wifi to avoid this. but would like to use the Ethernet on the dock as wifi signals in the building are too many and cause interference.
– Sid_Hussey
Jan 29 at 17:15
For other Surfaces we have put them on wifi to avoid this. but would like to use the Ethernet on the dock as wifi signals in the building are too many and cause interference.
– Sid_Hussey
Jan 29 at 17:15
So where exactly are you seeing the
BAD_ADDRESS error? Please edit the question to clarify this.– DavidPostill♦
Jan 29 at 21:36
So where exactly are you seeing the
BAD_ADDRESS error? Please edit the question to clarify this.– DavidPostill♦
Jan 29 at 21:36
Hi DavidPostil, Thanks for replying, I did mention it is in the DHCP server. To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
– Sid_Hussey
Jan 30 at 15:15
Hi DavidPostil, Thanks for replying, I did mention it is in the DHCP server. To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
– Sid_Hussey
Jan 30 at 15:15
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1399736%2fwindows-dhcp-issue-bad-address%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1399736%2fwindows-dhcp-issue-bad-address%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
For other Surfaces we have put them on wifi to avoid this. but would like to use the Ethernet on the dock as wifi signals in the building are too many and cause interference.
– Sid_Hussey
Jan 29 at 17:15
So where exactly are you seeing the
BAD_ADDRESSerror? Please edit the question to clarify this.– DavidPostill♦
Jan 29 at 21:36
Hi DavidPostil, Thanks for replying, I did mention it is in the DHCP server. To be more specific under Scope > Address Leases. So basically it is leasing out the IP but no one is getting those thus making it a BAD_ADDRESS. We do not have any other DHCP server running besides the Sonicwall which only provides IPs to wireless devices and VPN clients.
– Sid_Hussey
Jan 30 at 15:15