On Tuesday 19 July 2005 05:20, James Wright wrote:
I'm completely ignorant of VMWARE (along with, say, a few other things), but are you saying above that if, after having failed to reach a site on your SuSE box, you turn right around and launch VMWARE on that same machine, launch Win2K under VMWARE, and log into your Windows domain, that you can then reach these same sites that you can't reach under native SuSE?
Greg Wallace
Yes, that is correct.
How do you have vmware configured? Bridging or NAT?
Also, here is my ping and traceroute of www.sonicwall.com from a Suse PC (sorry it took so long, way too busy lately):
black-kdavzbpz3:/home/james # ping www.sonicwall.com <http://www.sonicwall.com> PING www.global.sonicwall.com <http://www.global.sonicwall.com> (64.41.140.167 <http://64.41.140.167>) 56(84) bytes of data.
--- www.global.sonicwall.com <http://www.global.sonicwall.com> ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms
Suspicious, but not necessarily conclusive, since not all sites respond to ICMP packets.
I don't really know what this tells me. It seems as though it works up to the 12th entry and dies?
Yeah, but it doesn't have to mean anything, since as I mentioned, not all sites respond to ICMP packets, and traceroute uses ICMP to do its thing
I am a little confused that I can resolve the IP, but the page will not load.
Well, the IP is resolved by your name server, which is separate from the remote web server. the name/ip mapping is maintained by a distributed database, usually not by the actual machine that is mapped You could try lowering your MTU a bit, say ifconfig eth0 1492 and see if that helps