[NTLUG:Discuss] No return packets from wellsfargo.com

[Kevin Brannen]

Dave Augustus wrote:

>OK Folks- I am going bald over this one. Any ideas?
>
>Here is the deal:
>
>My system has 2 hard drives,connected to the first IDE controller via a
>TRIOS hard drive switch. This allows me to select the BOOT drive which
>will boot either Windows XP or Redhat 9. My IP address is fixed for both
>OSes.
>
>When I select win, I can access wellsfargo.com without any problem.
>However, when I use Linux, I cannot get a RESPONSE from their webserver.
>I have reduced hosts.deny to nothing and turned off iptables.
>
>I have used tcpdump and found that DNS is returning IPs for the
>connection and that my machine is attempting the communication. Here is
>the tcpdump where my machine is waiting for an answer. Of course, the
>browser (I have tried Mozilla 1.7, Firefox and Konqueror) times out as
>well
>
>16:05:45.418840 DSL10-46.1scom.net.32822 >
>panpipe-dd.wellsfargo.com.http: tcp 0 (DF) (ttl 64, id 9972, len 60)
>16:05:46.284066 DSL10-46.1scom.net.32823 >
>panpipe-dd.wellsfargo.com.http: tcp 0 (DF) (ttl 64, id 44173, len 60)
>16:05:49.277082 DSL10-46.1scom.net.32823 >
>panpipe-dd.wellsfargo.com.http: tcp 0 (DF) (ttl 64, id 44174, len 60)
>
>TIA,
>Dave
>  
>

You don't need tcpdump to see of DNS is working, try a simple 
"traceroute wellsfargo.com".  It will show the IP on the first line 
(yours and the target).  You can also use "tracepath", similiar but just 
different enough it can be useful to try both.  That will also show you 
the route you will go thru to get there, and hopefully see where along 
the line you fail.  This can fail for various reasons, like firewalls 
that block ICMP packets, but it's still a good first test.

FWIW, http://wellsfargo.com works just fine for me on my Suse 9.0 system.

HTH,
Kevin