Users can ping website but cannot browse

[davidhvoss]

All users in one location (spread over two CMTS devices) can resolve homedepot.com to IP correctly when they ping it but they cannot browse if they put homedepot.com into their browser.  If they switch DNS servers from our DNS server (which other locations are using just fine) to 4.2.2.2, everything works fine - they can browse just fine.

The users are sourcing from multiple devices and subnets but they all are going out the same new Internet circuit. They were working fine until we pointed them out this new Internet circuit.  Routing to the subnets at this location from the Internet seems to work fine, we can reach the gateways of all IP addresses, but for whatever reason, all users cannot browse (but can reach via tracert) homedepot.com as well as 3 or 4 other websites.

Any thoughts?

[John Blakley]

davidhvoss wrote:
All users in one location (spread over two CMTS devices) can resolve homedepot.com to IP correctly when they ping it but they cannot browse if they put homedepot.com into their browser.  If they switch DNS servers from our DNS server (which other locations are using just fine) to 4.2.2.2, everything works fine - they can browse just fine.
The users are sourcing from multiple devices and subnets but they all are going out the same new Internet circuit. They were working fine until we pointed them out this new Internet circuit.  Routing to the subnets at this location from the Internet seems to work fine, we can reach the gateways of all IP addresses, but for whatever reason, all users cannot browse (but can reach via tracert) homedepot.com as well as 3 or 4 other websites.
Any thoughts?

"If they switch DNS servers from our DNS server"

Can the new location see your DNS server?

HTH,

John