Cannot access one IP address

0 pts.
Tags:
Networking
Tech support
I am running XP Pro w/SP2. I am on a large national domain. I must monitor a web site daily; up until a couple of weeks ago, it was working fine. Suddenly, I cannot access the site any longer, but only from my work computer. I can connect my laptop or login to a co-workers computer and I have no problem accessing the site. The IP address is 10.32.26.76. From my computer I can access 10.32.26.70, .74, etc. Tracert fails at the .76 address directly. I cannot find any settings that could cause this. Any idea's where I should look to resolve this?
ASKED: November 1, 2006  11:06 AM
UPDATED: November 10, 2006  7:51 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Are you getting a page cannot be displayed error?
Have you tried to add the site to your trusted sites?
Have you tried to use a different browser?
Have you checked to make sure you don’t have a hosts entry on your machine that could be causing the problem?
Have you tried to disable XP firewall and hit it again?
If you have access to firewall policies, have checked to make sure there is not a specific policy limiting just you from hitting this site?
Have you cleared out your temp internet files?
Just some quick troubleshooting thoughts.
Good luck.

Discuss This Question: 14  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Paulcat
    Error is "Oops, we can't open the web page you requested ... - Error Unknown - Unknown error with URL". I have tried 3 different browsers, but I can't even ping the address (no response) so trying different browsers doesn't really matter.
    0 pointsBadges:
    report
  • PhilReed
    This could be a routing issue. Check your subnet mask to ensure that you are on the same subnet. Do a 'route print' at the command prompt to check if a incorrect route has been added which directs you somewhere else.
    0 pointsBadges:
    report
  • Petroleumman
    Hello, Try running the command C:>ipconfig /flushdns which will clear your local dns cache. It is possible that a corrupt DNS entry was cached to your local machine and by clearing it may restore connectivty. Good luck!
    0 pointsBadges:
    report
  • Paulcat
    Thank you all for your quick responses. I have followed the suggestions to no avail. My IP address is 10.34.42.23, with a 255.255.255.0 mask. Route Print shows: Network Dest Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.34.42.1 10.34.42.23 20 10.34.42.0 255.255.255.0 10.34.42.23 10.34.42.23 20 10.34.42.23 255.255.255.255 127.0.0.1 127.0.0.1 20 10.255.255.255 255.255.255.255 10.34.42.23 10.34.42.23 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 10.34.42.23 10.34.42.23 20 255.255.255.255 255.255.255.255 10.34.42.23 10.34.42.23 1 Default Gateway: 10.34.42.1 I don't know if this indicates an incorrect route or not.
    0 pointsBadges:
    report
  • Douger
    Paul, You say that tracert fails at the .76 address directly. I would be suspicious of the router that is right before that. It may have an incorrect return route to you. Have you spoken to the administrator of that router?. D
    0 pointsBadges:
    report
  • Paulcat
    The trace is successful for a nearby address: tracert 10.32.26.76 1
    0 pointsBadges:
    report
  • Petroleumman
    Hello, Since the webserver (.76 address) is on the same subnet as your computer it should not be transversing a router, therefore the problem must lay somewhere between your local computer and the webserver. Anything beyond that would affect other machines on the subnet. From your computer run the command C:>ipconfig /flushdns to clear out any corrupt entries in your local DNS resolver cache. Now from the webserver run first C:>ipconfig /flushdns to clear the DNS resolver cache on the webserver, then run C:>ipconfig /registerdns to force a re-registration of the webserver's DNS information with the DNS server responsible for your subnet. Since you are able to hit the website from other computers on your subnet and your not transversing a router it leads me to believe that the problem is in the DNS resolver cache because if an entry (right or wrong) exists in the cache, this is where the process stops. It only moves up the chain if an entry is not available. Good luck!
    0 pointsBadges:
    report
  • Douger
    Paul, I disagree with petrol about routing. You are on subnet 10.34.42.xx, your web server is on 10.32.26.xx. Different subnets as far as I can see. The tracerts you posted are interesting. When you trace to the web server, the fifth hop is 10.32.25.2 . When you trace to the other address the fifth hop is the address you are trying to hit. I would suspect a problem in the routing tables on the 10.1.16.2 router. If you hook up your laptop or use someone else's computer, what does the tracert look like? Also, what ip address do you get? It could be that you are assigned an address in a different subnet, or that your coworkers computer has an address in a different subnet. This could produce different results. If you don't have access to the routers, I don't think that you will be able to fix this on your own. D
    0 pointsBadges:
    report
  • Douger
    Paul, Something else that is odd in your tracerts. The one that reaches it's destination ends with "request timed out" instead of "Trace complete". I'm not sure what would cause that, but it's not right. I'm still suspicious of router issues. D
    0 pointsBadges:
    report
  • Mortree
    I agree that there might be routing issues. But they might be using Variable Length Subnet Masks (variable sized subnets as well) at the end. I'd look back at the webpage message itself. "Oops!..." isn't a normal IE or FireFox internal mesage (you didn't mention browser type) but is a typical open source web server error message. So I am wondering if your home workstation is simply being blocked/filtered from accessing the page based on IP address.
    0 pointsBadges:
    report
  • Mortree
    Do not worry about failed pings and tracert's. Web servers (and some routers too) often block/ignore these to avoid the "Ping of Death" type Denial of Service attacks. Sometimes the blocking is based on IP. Home workstations are often less trusted than a IPs of a business partner or government office.
    0 pointsBadges:
    report
  • Petroleumman
    Ahhhh....my mistake. I see from a later posting that Paulcat's computer is on a seperate subnet than the webserver. My advice won't apply in this case. Good luck!
    0 pointsBadges:
    report
  • T2hieu
    I agree with Douger. Paul, check routing table on 10.1.16.2 router, also, check correct subnet and subnetmask for 10.32.26.xx T2Hieu
    0 pointsBadges:
    report
  • bmarone
    Routing is the most likely problem, given the differences between the .74 and .76 traceroutes. See if you can get a tracert from the webserver. On a private network, or even usually over the Internet, routes should hit the same routers forward and back. The 10.1.16.1 router should be fine, as both routes are the same to that point. Question why the .76 needs to be going thru the extra 10.32.25.2 router. It could be the webserver was recently dual-homed on the 10.32.25.x and 10.32.26.x networks, and it is favoring the 10.32.25.x route back to you. TCP connections would need consistent routes to work. If it's dual-homed, the webserver routes may need a permanent route added depending on who can't see the server and which solution is preferred: 1) Add a new static route to 10.34.42.0/24 using the 10.32.26.x router. 2) Change the metrics of the default routes 0.0.0.0 so the 10.32.26.x router is preferred. If my assumptions and the tracerts are all correct, the router is likely the 10.1.16.2 and has an interface 10.32.26.1 for that subnet. But a word of caution: some companies, esp larger corporations, would frown upon publishing IP address schemes and tracerts on a public website. If you don't own the network or the webserver, careful how you present your ideas towards the problem. Also for a large corporation, there should be some change-mgmt/trouble ticket from the timeframe the website became unreachable, either for the webserver or its gateway router. Maybe someone can find this ticket to determine what happened.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following