Might compare the results of
ipconfig /all
tracert 8.8.8.8
between working and non-working.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a comcast Business Router that is hooked into a Juniper SRX300 firewall. Then the Firewall is plugged into the Aruba 2530 Switch. The problem I experience is some of the endpoints will connect with no problem to web pages. And some will not saying the error is failed to connect DNS issue. Why would this only be on some computers and not all if it is a DNS issue? I'm completely dumfounded by this. Please advise. Also one laptop that is doing it on the network doesn't do it on another network.
Might compare the results of
ipconfig /all
tracert 8.8.8.8
between working and non-working.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Hi,
Welcome to Q&A platform.
I noticed that some third-party devices were involved in your environment, and the issue only occurred on some clients, some clients were working well. Before we go further, I would like to know if the DNS settings were configured same on both working and non-working scenarios? Which website cannot be accessed?
I would suggest you could run the following command in a cmd window with administrator privilege on both working and non-working clients to see if there is any differences. Or you could post the results with removing any private information of you or your company for further troubleshooting.
nslookup -d2 domain name of the problematic website
Best Regards,
Sunny
----------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Just checking if there's any progress or updates?
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This issue was resolved. It was the cradlepoint causing the two different IP addresses. Once removed the IP stayed same.