RE: Can't see some web pages after Server 2003 install



Most likely a routing problem between somewhere between you and the
destination, might be worth contacting your ISP.

If you do a traceroute (pending you permit icmp traceroute packets etc
through your firewall) to a 63. address, what are the results?


Cheers, Simmo

"teleute" wrote:

> Hi all;
>
> Hopefully someone can help me with this - I'm trying to help a friend, who's
> been struggling with this for a while, but I haven't made much headway. Ever
> since installing Win Server 2003 and going to a client/server model (it had
> just been p2p before), there have been a number of web sites that people have
> have been unable to reach. I was checking these out and noticed the IPs for
> these sites all begin with 63. In fact, every unreachable site begins with
> 63, and as far as I can tell, every 63 site in unreachable. They're just
> using the basic firewall under Routing & Remote Access - I've tried turning
> that off and it doesn't seem to make any difference. Does anyone have any
> idea as to what might be causing this? Thank you.
.



Relevant Pages

  • routing problem
    ... I have the following routing problem: ... IP 1.4.13.29 which is behind a firewall. ... If I do for example a traceroute to ... Route Tree for Protocol Family 2: ...
    (AIX-L)
  • Re: Any famous C++ project in open source Linux?
    ... compilers. ... BOFH excuse #280: ... Traceroute says that there is a routing problem in the backbone. ...
    (comp.os.linux.development.apps)
  • Re: Explosions - Fuel Depot
    ... Traceroute says that there is a routing problem in the ... backbone. ... Prev by Date: ...
    (uk.media.tv.misc)