Having Internet Problems

I've tried several iterations and still have not succeeded in getting my guest to access the internet.

Current setup:

Mac - Airport

• 192.168.0.1/255.255.255.0 (DHCP-manual)
  Gateway 192.168.0.56
• DNS set to cable company DNS servers
• sharing is off

Mac - Guest Adapter

• 10.37.129.2/255.255.255.0 (DHCP)

Parallels Guest - WinXP

• Bridging to Airport
• Using ipconfig: 192.168.0.2/255.255.255.0
  Gateway 192.168.0.56
• successfully pings parallels.com

IE won't connect and gives the error page like it has a DNS problem.

Any suggestions?

 

rammjet,

If an XP VM can 'ping parallels.com' or any other site for that matter, then you certainly are connected. You can simulate web browser activity like that:
1. In XP click Start then 'Run...'. Type 'cmd' and click OK.
2. In a terminal window that will appear type 'telnet parallels.com 80'. Terminal window should go black with cursor bar blinking in upper-left corner.
3. Type (note: you'll be typing blind) 'HEAD / HTTP/1.0' and hit Enter key twice. If a text response appears starting with line 'HTTP/1.1 200 OK' then the problem definitely lies on IE part. Check HTTP proxy settings in IE.

 

serv,

The command "telnet parallels.com:80" connected but the "HEAD" command wasn't accepted. Probably a syntax error or I typed it wrong. But telnetting confirms connection.

IE has no proxies set - it is all default from a fresh install. I'm no Windows expert, but it is like IE cannot resolve DNS.

 

rammjet,

Hmm... You can type 'HEAD / HTTP/1.0' in Notepad, select the text and then paste it to telnet window. I would make several attempts on that, because this simple test may pinpoint the problem.
There's no indication that your problem is DNS related. Both ping and telnet did resolved parallels.com just fine. IE error reporting is confusing most of the time. You can try typing 'nslookup parallels.com' and see if it resolves to 66.197.23.53.

 

Except for the one time where the "HEAD" word was rejected, all other attempts prior and since to telnet to parallels.com have FAILED with the message: "could not open connection to the host, on port 80: connection failed"

However, nslookup first lists my router IP and then lists 66.197.23.53, so DNS is working.

I should note that no other internet app can connect to the internet either.

 

rammjet,

Seems we're back to basic troubleshooting:
1. Do you have a firewall on your Mac? Try turning it off. Also turn off Windows firewall just in case.
2. Check if your router is doing MAC filtering (allows only known MAC addresses).
3. Try wired ethernet, if possible, and see if it makes any difference.
4. Issue 'tracert parallels.com' from XP and 'traceroute parallels.com' from OSX and look for any differences in routes.

 

serv:

1. No firewall on Mac or Windows. Firewall provided by router.
2. No MAC filtering in router.
3. Wired is too hard. Cable modem on 2nd floor.
4. Tracerts are identical for Mac and Windows.
5. telnet from Windows still fails
6. telnet from Mac succeeds, but HTTP response is 'HTTP/1.1 400 Bad Request'

 

rammjet,

Do I understand correctly that your wireless AP is connected directly to cable modem and is not providing NAT for your local network? If yes, your contract to cable company should allow you to use more than one IP address. It's surprising however that ICMP packets still pass through...

As a workaround you can use Host-Only mode with Internet Sharing. Refer to PD manual for instructions on how to set it up.

 

serv:

My wireless router is connected to the cable modem and it DOES provide NAT for my local network.

I give the Mac a manual IP for personal reasons, but everything else is DHCP. And you can see that in the IP's in my first post.

Thanks!

 

In OS X, in the Applications-Utilities folder, launch terminal and enter:
ifconfig

Now open the guest OS and enter:
ipconfig /all

Paste both back here so we can look at what's going on. Alternatively, open your Applications-Utilities-Network Utility application in OS X. Get the IP address. Make sure you can ping an external site (e.g., ping www.apple.com). Open the guest and ping the host (e.g., ping 192.168.0.2). If you are using a static IP address (one you entered), make sure the Mac side and the guest side are using two different IP addresses.

If the ping succeeds, go back to the Mac side and lookup the IP of a well known site:
foo:~[bar] $nslookup www.apple.com
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 144.243.35.244
Address: 144.243.35.244#53

Non-authoritative answer:
www.apple.com canonical name = www.apple.com.akadns.net.
Name: www.apple.com.akadns.net
Address: 17.254.0.91

Take that IP address and try to ping it from the guest. If it succeeds, you have a firewall or some other software blocking your web access. Check the logs - Applications-Utilities-Console - System log, Console log, and the Firewall log (ipfw).

 

rammjet,

What model your wireless router is? There must be something special about it, since it routes ICMP but not TCP for the VM.

 

serv:

The router is a Linksys WRT54G v1.0 with Sveasoft Alchemy installed.

Edit: all other computers I've used on my system have successfully used the Linksys to access the internet.

 

MicroDev:

Per your request, ifconfig and ipconfig:

Code:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	inet 127.0.0.1 netmask 0xff000000 
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
	ether 00:15:f2:e3:4e:fb 
	media: autoselect status: inactive
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <half-duplex,hw-loopback> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <half-duplex,hw-loopback> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
en1: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
	ether 00:15:f2:e3:45:37 
	media: autoselect status: inactive
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <half-duplex,hw-loopback> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <half-duplex,hw-loopback> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::230:bdff:fef3:5eec%en2 prefixlen 64 scopeid 0x6 
	inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
	ether 00:30:bd:f3:5e:ec 
	media: autoselect status: active
	supported media: autoselect
fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 2030
	lladdr 00:11:d8:00:00:96:e3:5a 
	media: autoselect <full-duplex> status: inactive
	supported media: autoselect <full-duplex>
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::201:23ff:fe45:6789%en3 prefixlen 64 scopeid 0x8 
	inet 10.37.129.2 netmask 0xffffff00 broadcast 10.37.129.255
	ether 00:01:23:45:67:89 
	media: autoselect status: active
	supported media: autoselect

Code:

Windows IP Configuration
        Host Name . . . . . . . . . . . . : none-71d93b6224
        Primary Dns Suffix  . . . . . . . : 
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : atlsfl.adelphia.net
Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . : atlsfl.adelphia.net
        Description . . . . . . . . . . . : Parallels Network Adapter
        Physical Address. . . . . . . . . : 00-22-E1-86-F0-BE
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.2
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.56
        DHCP Server . . . . . . . . . . . : 192.168.0.56
        DNS Servers . . . . . . . . . . . : 192.168.0.56
                                            68.70.15.244

                                            68.70.15.245
        Lease Obtained. . . . . . . . . . : Wednesday, June 28, 2006 11:33:14 AM
        Lease Expires . . . . . . . . . . : Thursday, June 29, 2006 11:33:14 AM

 

MicroDev:

the Guest can ping the Mac's IP address and apple.com IP address.

the Mac CANNOT ping the Guest's IP address but can ping apple.com IP address.

Edit: both the Mac and the Guest have firewalls turned off.

 

serv:

I have TWO onboard ethernet ports. Is it possible that there is some internal confusion over en2 and en3 because of the extra port?

 

rammjet,

Your hardware is looking weird to me: 2x wired ASUSTEK ethernet interfaces and BELKIN wireless(?) card. What Mac model is this?
In the first post you've indicated your router is 192.168.0.50. But in XP it is set to 192.168.0.56. Is that OK?
You should be able to telnet/ssh to your router and issue '/sbin/arp -a' to see if VM IP is associated with the right MAC. What's in there?

MicroDev, thanks for asking the right question

 

serv:

It is a "special" Intel Mac model. The Belkin card was pulled from my (PPC) G4 Mac which didn't have 54G capability.

And yes, the routers are OK, I was "cleaning" the IP's for public consumption. The 50 should be and has always been 56 on my network. I'll edit the first post for consistency.

 

There are no real Intel Macs that support more than 1 Ethernet interface yet. Let me guess. It's a PC running a pirated copy of OS X for Intel...

 

serv:

I used the web interface to query the router and under DHCP it shows the Guest at IP 192.168.0.2 and MAC 00:22:E1:86:F0:BE as well as the router and Vonage adapter. The Mac is listed under Wireless (I suppose since it is a manual IP setting) along with a few other wireless devices I have.

 

rammjet,

knowing router DHCP state for the VM is not enough... Fortunately your router is running Linux with all the tools we could use for debugging. You should enable telnet (simpler) or SSH (more complicated) on the router via web interface. Then telnet to it and issue '/sbin/arp -a', this will show ARP table of the router and 192.168.0.2 entry should map to 00:30:bd:f3:5e:ec.

Well, I just though of one experiment you can try. Configure XP with static address of your "Mac" and see if IE works now. You will loose networking in OSX, but it will recover when you shutdown XP.
BTW, if you've set the VM bridged networking to 'Default Adapter' try setting it to 'en3: Airport/Wireless'.
And one more question... What's your OSX version? Is it higher than 10.4.5?