This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 91%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
I have an IoT Edge device that is unable to connect to my IoT Hub. This device connects fine on any other network. I'm nowhere near any quotas or limits. The IoT Hub is otherwise working perfectly for other similar devices on different networks having the same Deployment.
It appears that the IP address/block of this network (Xfinity) may be being blocked?
If I do a traceroute to my IoT Hub host, it dies at the first Microsoft server it touches (..dsm05.ntwk.msn.net).
Any ideas how I can chase this down?
Here's the output of iotedge check: https://gist.github.com/kpm-at-hfi/dcd951b996aae5a91d9747a64744a541
(Couldn't just post here because to 1000 character limit.)
@Ken Martin thanks for bringing your issue here. I have changed the tag to azure-iot-edge as it is more appropriate.
1) Did you try connecting your IoT Edge device to a different network and give it a try?
2) Take a look at the following documentation, I suspect you will need to configure your IoT Edge Device to work behind a proxy server: https://learn.microsoft.com/en-us/azure/iot-edge/how-to-configure-proxy-support?view=iotedge-2018-06
Per #1, yes and it works as expected.
Per #2, I am certain there is no proxy server in place. Also, there are no firewall rules or other security measures in place.
I'd chosen azure-iot-hub only because azure-iot-edge is working perfectly... it's only acccess to the hub itself that is the problem.
@Ken Martin by a different network I mean to use another Wifi\ethernet connection. Can you confim when you are on a different network it works?
Thanks
Yes, I've tried both different places on the LAN and WLAN (with no success) and also different networks connected to different WANs (with success).
Here's a traceroute from the device from within the problem network: https://gist.github.com/kpm-at-hfi/e7fc1fd09a855601b39a290c5c36bc53
I understood it better now. Can you confirm what is the region you have deployed your IoTHub? I will escalate this with the note that you suspect " network (Xfinity) may be being blocked".
Thanks!
"Central US"
Thank you!
@Ken Martin just dropping a note that this is being looked at. Sorry for the time it is taking. Let me know if you see anything different from reported so far.
Thanks!
Hello @António Sérgio Azevedo ... I'm very sorry for the delay!
That didn't work. It was the host network... not Comcast. I swapped out the router at the location and all was well.
I'm sorry for the false alarm and thank you for helping me out.
You are welcome @Ken Martin please reach out as needed. Can you go ahead and add your own answer to the thread and verify it as answer to help others? Thanks :)!
Hello @Ken Martin thank you for your patience in advance.
We notice that Comcast network is involved, therefore you are trying to connect to the IoT hub from your on-premises. Can you confirm?
I have researched internally and there is no evidence that the Xfinitiy network is being blocked.
Can you try to run vanilla ubuntu container in the azure-iot-edge network and check if you can connect to the iothub?:
# start ubuntu container inside azure-iot-edge network
$ docker run --rm -it --network="azure-iot-edge" ubuntu
# inside container and check it can connect and verify TLS connection with iothub
openssl s_client -connect -showcerts YourIoTHub.azure-devices.net:443
Thank you!
Hello @Ken Martin ,
Let us know if you are still blocked or if you have tried the suggestion above?
Thank you!