Ubuntu 7.10 Guest on XP Pro Host: Networking Issues

L

LongFist

Bit poster
Hey there! I am amazed at how (relatively) simple it is to build a VM in Parallels (under WinXP/Pro). I managed to get my Ubuntu 7.10 up and running in a little less than five hours (for some reason, the installation took its own sweet time...), and after installing the Parallels Tools I can play with Ubuntu just like any other WinDoze app. But (for some unspeakable reason) I have no network connectivity from the Guest OS.

Oh, it lets me tool around with the Network Settings, and makes like it's going to get somewhere, but I cannot ping the Host machine, and I cannot get anything else, either.

An interesting observation: I told my "Parallels Host-Guest Virtual NIC" to use DHCP (as the hardware/host does), and then told my Guest OS (Ubuntu) to do the same. If I go to a command prompt in WinDoze and type "ipconfig all", I can see where the "Parallels Host-Guest Virtual NIC" is connected to the network, as xxx.xxx.xxx.2 - no big deal. But if I open the terminal in Ubuntu and type "ifconfig eth0 -a", I get a reported IP of xxx.xxx.xxx.44!!! Could this be part of the issue? Because my Ubuntu is deaf as a post...

...the main reason for doing this is so I can run my network monitor(s) [etc.] without having to dual-boot my poor notebook. So far, the notebook appears to be holding up well under the strain, except I cannot seem to perform any network activities.

<A> Is this the normal behavior of Parallels (networking), sort of like the two IPs you use with a Router that connects you to your ISP, or should those numbers match up?

[ The fact that I'm writing this message on the afflicted computer lends some credence to the claim that it (normally) connects to the network/internet without any hassles. ]

Has anybody else seen/heard/observed this type of behavior? Is there any way to get this Guest OS connected?

Thanks in advance,
 
13 Days --- No Response in sight!

13 Days. Wow. Good thing I'm still working on it. At Microsoft, we were only allowed the accrual of 2 days before requiring at least a callback. I'm assuming that either (a) the Techs are cherry-picking the support messages, or (b) the Techs ignore the Windows side of Parallels. <frown> Ah, well, I guess it's to be expected. I've read other messages, and seen the lack of response before. This would be a good time to develop a web-based knowledge base (hint hint), so the users could browse through a list of break/fixes, and not depend on a forum that's passively being ignored.

As far as I could see, the previous message was a detailed request for help. Instead of name-calling, arguing, finger-pointing, knit-picking, and the like, it attempted to describe a situation in the hopes that someone, somewhere, had seen or understood what was happening. I guess being nice doesn't gather attention. But you know, guys, we (the users, clients, purchasers of your product) also talk amongst ourselves. Yes - it's true! and sometimes, we change our opinions from "best thing since sliced bread" to something less ecstatic. Until this week, I had sung praises to your product. High praise. Maybe I was premature...
 
Is this normal?

Status Update: I suspected that the Parallels VM Editor needed some detail surrounding the network connection. I then added another network connection, and assigned each (now there were two) to the various hardware that supported it - eth0 was assigned to my 10/100 LN Card, eth1 assigned to me Wireless 802.11b/g interface. Since I turn off the radio/modem on my wireless, that particular connection should have remain inert. However, since my machine connects to the 'Net via 10/100 hardwire interface, functionality should have been restored. No dice. And while there were two interfaces, both defaulted to "Default Adapter". Eh? What gives? So I removed one of the network interfaces - since it made no difference to the Parallels VM Editor as to where these devices should be pointing...


Problem: Assign eth0 to my 10/100 LAN card directly, instead of "Default Adapter". At restart of VM, defaults back to "Default Adapter". Networking still inoperable from guest machine.
 
There is three different way to have internet connection in your guest VM OS>

1. Bridge
2. NAT
3. Host Only Network

Have you tried any of this? Let's try..........


_______________

SakibS
text-smiley.png
 
You must log in or register to reply here.
Back
Top