On Monday, July 18, 2005 @ 7:21 PM, 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. 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
black-kdavzbpz3:/home/james # traceroute 64.41.140.167 <http://64.41.140.167> traceroute to 64.41.140.167 <http://64.41.140.167> (64.41.140.167 <http://64.41.140.167>), 30 hops max, 40 byte packets 1 172.16.200.17 <http://172.16.200.17> 7.877 ms 7.005 ms 6.817 ms 2 vtelinet-216-66-108-205.vermontel.net <http://vtelinet-216-66-108-205.vermontel.net> (216.66.108.205 <http://216.66.108.205>) 6.788 ms 6.857 ms 7.494 ms 3 g11-2.core01.bos01.atlas.cogentco.com <http://g11-2.core01.bos01.atlas.cogentco.com> (38.112.23.169 <http://38.112.23.169>) 18.955 ms 17.997 ms 17.938 ms 4 p5-0.core01.jfk02.atlas.cogentco.com <http://p5-0.core01.jfk02.atlas.cogentco.com> (66.28.4.118 <http://66.28.4.118>) 22.829 ms 22.693 ms22.559 ms 5 p4-0.core02.dca01.atlas.cogentco.com <http://p4-0.core02.dca01.atlas.cogentco.com> (66.28.4.81 <http://66.28.4.81>) 29.631 ms 29.606 ms 29.411 ms 6 p14-0.core01.iad01.atlas.cogentco.com <http://p14-0.core01.iad01.atlas.cogentco.com> (154.54.2.198 <http://154.54.2.198>) 95.433 ms 62.297 ms 29.063 ms 7 cpr1-ge-8-1.VirginiaEquinix.savvis.net <http://cpr1-ge-8-1.VirginiaEquinix.savvis.net> (208.173.10.181 <http://208.173.10.181>) 29.759 ms 30.020ms 30.395 ms 8 dcr1-so-6-1-0.Washington.savvis.net <http://dcr1-so-6-1-0.Washington.savvis.net> (208.173.52.114 <http://208.173.52.114>) 30.189 ms 29.924 ms 57.266 ms 9 bcs2-so-5-2-0-500.Washington.savvis.net <http://bcs2-so-5-2-0-500.Washington.savvis.net> ( 204.70.192.162 <http://204.70.192.162>) 30.418 ms 30.548 ms bcs1-so-5-0-0-500.Washington.savvis.net <http://bcs1-so-5-0-0-500.Washington.savvis.net> (204.70.192.170 <http://204.70.192.170>) 30.952 ms 10 dcr1-so-5-0-0.SanFranciscosfo.savvis.net <http://dcr1-so-5-0-0.SanFranciscosfo.savvis.net> (204.70.192.149 <http://204.70.192.149>) 96.613 ms 96.045 ms 96.089 ms 11 bhr1-pos-13-0.SantaClarasc5.savvis.net <http://bhr1-pos-13-0.SantaClarasc5.savvis.net> (208.172.147.110 <http://208.172.147.110>) 96.581 ms 96.517 ms 96.834 ms 12 csr1-ve242.sc4.savvis.net <http://csr1-ve242.sc4.savvis.net> (216.34.2.243 <http://216.34.2.243>) 97.105 ms 96.622 ms 96.664 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * black-kdavzbpz3:/home/james #
I don't really know what this tells me. It seems as though it works up to the 12th entry and dies? I am a little confused that I can resolve the IP, but the page will not load. Thanks for all the help so far, you guys are great.
James W
This is getting a little over my head here, but I keep thinking it might be a security issue. I believe you indicated (or maybe I'm reading between the lines) that you aren't using Samba to connect to your LAN when you're running SuSE, but you are logged into your network when you launch VMWARE/Win2K. Maybe VMWARE/Win2K is routing through your LAN and picking up some security privilege that that isn't available trying to hit your WAN directly (bypassing the network). If all else fails, you might want to look at setting up Samba and joining your Linux box to the domain. Greg Wallace