Unable to navigate using IP yet can browse using URL

[rockiwood]

Thanks for advice in advance.

My problem is this:
On our network we are using an IP address to navigate to a particular website on the WAN which is not at our location.

I installed the latest Windows Updates, rebooted the Server, which is also the DNS server locally. Now I can browse the Internet, yet am unable to navigate to the website using the IP address. I can navigate to it using the FQDN. The address can be PING'ed with no problem.

I can browse to any website without problems.

In addition I can no longer Remote Desktop using IP, but can using Name.

I can navigate to an HP printer using IP.

I have removed 3 of the updates that were installed before the reboot to no avail.

What would make IP navigation stop working yet everything else is working?

I hope I explained this properly.

Jerry

 

[LawnBoy]

Sounds like you're using the wrong IP address, while DNS has the correct one. Ping by name and then by IP to see if the addresses match.

 

[rockiwood]

Right IP and I can ping it. Remote Desktop settings are correct also. All the addresses had been used over the last year and had been saved. I contacted an admin on the WAN not at my location and everything works for him.

Thanks,

Jerry

 

[LawnBoy]

Well, see, DNS is simply taking the FQDN and returning the IP. Your browser is using the IP addy even though you see it as a FQDN.

Do you have an entry for that server in your local HOSTS file?

 

[rockiwood]

This is a crazy problem. I know what you are saying and have checked everything. Straight IP needs no resolution and should work.
All workstations (50 or so) are having the same problem, since they are set to DHCP from this server.
If I go to 10.50.10.50 (Ex), the browser just grinds away and never brings up the website. If I go to the FQDN, it works okay. I have checked wiht the guys form that location and they say nothing has been changed.
If i try a Remote Desktop to another IP, no connection. If I use the Computer name, it connects.

I have checked for viruses, etc. DNS and DHCP is working great.

Crazy problem.

Thanks Again for the response

 

[LawnBoy]

If you ping the FQDN it shows the correct IP?

Crazy indeed.

At this point I would fire up Ethereal (WireShark) and capture a FQDN connection attempt and an IP attempt and compare them. Excluding the DNS lookup, they should be identical. Obviously they're not...

Good Luck.