Sunday, September 13, 2020

Device doesn’t appear to be communicating to the public IP of the network it resides on outside of HTTP

I have an odd issue that I wanted some help with. I have a device that is able to navigate to the public IP to display the webpage hosted on 80/443, but it seems that other services are failing and in an odd way. The host won’t even generate the requests or at least Wireshark isn’t capturing them. If I ping, no packets are captured, if I run the web application that started me on this rabbit hole, no packets are generated either. It is almost like the computer thinks it can’t get there and doesn’t even try – yet it can get there via web browser.

Many people have insisted it is DNS, but I’m not sure what about the DNS is wrong. If I do nslookup it resolves, if I ping the domain name it resolves the IP, and if I ping the IP directly it still doesn’t generate ICMP traffic in Wireshark. If I ping other domains/IPs the traffic shows up as expected. I have considered putting a static route in the host file, but this is for a laptop that will be used outside the network and be expected to still have access to this resource.

Does anyone have any ideas about what is happening here?



No comments:

Post a Comment