VMware Communities > VMTN > Desktop Products > VMware Fusion > Discussions

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
3 Replies Last post: Jul 18, 2008 11:58 AM by stevenkan
Reply

NT4 VM imported from Parallels, networking doesn't work

Jul 17, 2008 12:19 AM

Click to view stevenkan's profile Novice stevenkan 11 posts since
Jul 17, 2008
I had this VM running NT 4 SP6a in Parallels. I uninstalled Parallels Tools, installed the VMWare Converter 3.something and ran it, saving the converted VM to a network volume. I then copied the entire VM folder to my local hard drive and ran it. I then installed VMWare Tools, updated the video driver, rebooted, removed the RealTek NIC left over from the Parallels VM, rebooted, installed the AMD PCNet Family adapter, allowed it to copy necessary files from a folder containing the contents of an NT4 SP3 install CD, rebooted, reinstalled SP 6a, and rebooted.

The networking isn't working. If I choose Shared or Host Only networking with DHCP, I don't get an IP address. When I choose Shared, does Fusion run a little DHCP Server and NAT router?

When I choose Bridged (which is what I really want to use), I get an IP address, but I still can't see any network shares or connect to any webservers. I'm rebooting NT every time I change networking options in Fusion.

I can't even ping the router that just gave me the IP address! ipconfig /all gives me:

Windows NT IP Configuration

Host Name . . . . . . . . . : parallelsnt-01.pv.oc.cox.net
DNS Servers . . . . . . . . : 192.168.1.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter AMDPCN1:

Description . . . . . . . . : AMD PCNET Family Ethernet Adapter
Physical Address. . . . . . : 00-0C-29-07-AC-58
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.193
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . : Thursday, July 17, 2008 12:11:43 AM
Lease Expires . . . . . . . : Thursday, July 17, 2008 4:11:43 AM

That lease time is correct (e.g. right after I booted). But oddly enough, if I do ipconfig /renew, it times out with a "Error: DHCP Server Unavailable: Renewing adapter "AMDPCN1"

It almost seems like it works for a very short period of time at boot, but then something starts to block or interfere with it. The OS X firewall is completely turned off. NT's Event Viewer shows the only error being NETLOGON: domain controller couldn't be contacted, which could also be because I'm at home right now.

Any other options out there? I really don't want to have to completely rebuild this VM, because there's a lot of stuff to do.
Reply Re: NT4 VM imported from Parallels, networking doesn't work Jul 17, 2008 10:23 AM
Click to view etung's profile Guru etung 10,543 posts since
Oct 15, 2006
VMware
If you try with another virtual machine (I like using DSL because it's small and so is fast to download), does networking work? This will help narrow down if this is a Fusion-wide problem or specific to the converted virtual machine.

What does `ifconfig` in OS X's Terminal.app say?
Reply Re: NT4 VM imported from Parallels, networking doesn't work Jul 17, 2008 11:10 AM
Click to view WoodyZ's profile Guru WoodyZ 9,220 posts since
Apr 22, 2004
To add to what Eric said if you do download DSL you should try assigning it as the CD/DVD on the Virtual Machine you're having an issue with and boot the dsl-4.4.3.iso image and DSL should automatically be able to connect to the Network if the Virtual Machine is configured properly and connectivity exists on the Host. If it doesn't then this would indicate an issue with the Virtual Hardware and or the VMware Network Background Services. You do not actually need to install DSL in a new Virtual Machine to troubleshoot where your issue may be.
Reply Re: NT4 VM imported from Parallels, networking doesn't work Jul 18, 2008 11:58 AM
in response to: WoodyZ
Click to view stevenkan's profile Novice stevenkan 11 posts since
Jul 17, 2008
attempting to reply via email, since web posting has failed 3x now

Hmmm. I left in bridged mode and assigned myself a static IP in the same
subnet. Everything worked! So I switched back to DHCP, and everything
worked! Strangely enough, it pulled the exact same IP that it pulled
when it wasn't working. I was also patting my head and rubbing my
stomach at the same time, so maybe that's what fixed the problem.

But thanks to all for the suggestions. They'll be useful for other
troubleshooting down the road, I'm sure.
Actions