![](https://seccdn.libravatar.org/avatar/70ca5299a70a37eb74766675ae27ab54.jpg?s=120&d=mm&r=g)
On 7/20/05, James Wright <jwright@blackriverproduce.com> wrote:
I'm gonna venture a guess that the problem has to do with routers outside of your network. Based on dns working and the fact that you can route out of your network up to a certain point. Ethereal should reveal more about what's happeining.
John
What exactly would I look for in ethereal? I have it and can run it, but the results are relatively meaningless to me.
James W.
You should capture packets from the Windows box that works and compare to packets from the SuSE box that doesn't. Ping and traceroute are good tools to get started with, but they don't provide alot of information. Dns works as has been determined by pinging by name. You can route out of your network, as has been determined by traceroute. But you're not going to get much farther than that with those tools. As for what you should look for. You should see the the dns query for www.sonicwall.com and then the traffic to and from the web server including any errors. For all we know the server could be allowing your Windows box to connect, but for some unknown reason, not responding to your SuSE box (not responding to the handshake or the http request, etc.). I don't buy the reason I just stated because my SuSE boxes can hit sonicwall.com just fine. It's just an example. Or (another example), the SuSE box does its dns query, gets a reply from the local dns server, but then can't get the http packets out of the network. The firewall logs should show if the http packets are getting out. Ethereal can show you all this. as well as the difference between the packet sizes of the Windows box and the SuSE box. Maybe a router isn't happy with your packet size and is dropping them, but your packets (traceroute packets anyway) are leaving your network based on traceroute. After that, who knows. It's either it's router has route table issues or it doesn't like the packets from your SuSE box. If it's a route table issue, then more than just yor SuSE box should have problems if they all follow the same route, and more people than you would be having problems also. If it isn't a route issue, then it's back to your SuSE box and how it's networking is setup or something on your local network (i.e. firewall, traffic shapper, etc.) that is affecting the traffic from the SuSE box. John