-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Nick Wiltshire wrote:
> On Monday 27 March 2006 11:21 am, Hendrik Schaink wrote:
>> What does your /etc/resolv.conf look like?
>>
> 
> nameserver 192.168.1.5 (internal cache)
> nameserver 64.59.135.133 (shaw)
> nameserver 64.59.135.135 (shaw)
> 
> but my DNS is working...it just refuses to connect to websites on a "roaming 
> blackout" basis. It's not much fun to track down.
> 
> I also just received email 4 days old, all from telus addresses. (I run a 
> mail 
> server here)
> 

That is not surprising.  The headers of the email messages should help
in tracking down the mail problem.

Probably the easiest thing to try first is to connect a machine directly
to your cable modem, and then trying to connect.  Next would be to use
RDP or ssh + links/elinks/lynx/w3m to check connectivity from a remote
site.  Telnetting to port 80 does nothing, you need to send data first
before the http server replies.  Also, try connecting from a console
program, I like elinks, but any should work.  The site worked for me on
my workstation (using both elinks and firefox under linux), though there
is a flash intro (is flash installed and working?)

You may wish to run ethereal to capture your browsing attempt.

> Hmmm...
> 
> Nick
> 
> 
>> Mine is like this:
>> (infovisi.com = internal domain name,
>> 192.168.0.3 = internal DNS server):
>>
>>      search infovisi.com
>>      nameserver 192.168.0.3
>>
>> HTH,
>>
>> Hendrik Schaink
>>
>> Nick Wiltshire wrote:
>>> Hi all,
>>>
>>> I have a very odd & hard to debug connection issue. I can surf 99% of the
>>> web, send/receive email, P2P, Bittorrent, IM....everything. Except the
>>> occasional website...right now it's voodoopc.com. I can access it from
>>> everywhere except on this side of my firewall....leading me to wonder if
>>> it's a routing problem? I have a WRT-54G and a Linksys 16 port switch.
>>> This particular machine is hooked directly to the router, but I've tried
>>> 2 other machines on my network as well, both hooked to the switch, which
>>> is hooked to the router. The DNS is resolving correctly.
>>>
>>> I'm out of ideas, can someone lend me a clue?
>>>
>>> Nick
>>>
>>> _______________________________________________
>>> clug-talk mailing list
>>> [email protected]
>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>>> **Please remove these lines when replying
> 
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEKEtkwRXgH3rKGfMRAuZ1AJ4gSNcpod6twxVVROW34natMiyUzQCcDnp5
a3l9S4EcHPpuvD3Svac1/5U=
=ZWC1
-----END PGP SIGNATURE-----

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to