Network not working after Windows 2000 SP4 P2V

[kac2]

It has been a roller coaster getting this machine virtualized.

A little background: This machine is Windows 2000 SP 4 with update Rollup 1. After installing Update Rollup 1 I tried virtualizing it and it gets to 97% and then i get the error message " vmware agent has encountered an error". When I try to boot the machine I get a BSOD with an inaccessible_boot_device error.

After reading through a bunch fo threads I found a solution by reconfiguing the virtual machine so it will boot. So now I have a virtual machine that will boot.

Now my problem is that networking isn't functioning at all. I have removed the network adapter, added a new one, tried static and dhcp, gone through the Add/Remove Programs and uninstalled every HP and Compaq device, gone through the Device Manager and removed every HP and Compaq driver or component, rebooted countless times and I'm still ending up with no network connectivity.

The network adapter on the VM says it's connected and it says it's recieving, but not sending. It's not pulling a DHCP address and a static address gets no where also.

I have over 50 VMs so I know it isn't a problem with my network, this has to be on the VM itself. I don't know what else to try and I'm open for suggestions.

Thanks!

[jayolsen]

check this thread. http://communities.vmware.com/thread/94875

[kac2]

i tried everything in that paragraph and still it's not working. just can't seem to get network connectivity

[jayolsen]

ok. In the VM if you go to Edit Settings and select the network adapter, does the device status have Connected and Conect at power on checked?

[Troy_Clavell]

can you try updating the network drivers in device manager. Point the update to the VMware Tools install Directory C:\Program Files\VMware\VMware Tools\Drivers\vmxnet

[kac2]

The adapter sayd 'Connected' and 'Connect at Startup'. I have tried updating the Nic drivers and still resulting in no network connectivity

[jayolsen]

Could the vswitch the VM is connected to be out of ports? You said you have over 50 VMs, are they all on one vswitch? The default number of ports is 56 if you added the vswitch after the installation process.

[kac2]

that's not the problem because there are 7 ESX servers each with their own 56 port switch

[kac2]

when i try to do an ipconfig /renew i'm presented with the following

Windows 2000 IP Configuration

The following error occurred when renewing adapter Local Area Connection 2: An internal error occurred. Disconnect and reconnect the network interface or reboot the machine

I've done all of those and still no network connectivity

[jayolsen]

Got me, sounds like you have tried about everything I'd have tried. Could you try doing a p2v again not select not add a network adapter during the creation. Then once the conversion is complete, go in and remove the HP agents and nic teaming software if present. Then after removing all that and rebooting, add in a nic at that point.

[kac2]

i'll give it a go. thanks jay

[Texiwill]

Hello,

Moved to the Virtual Machine and Guest OS forum.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll

Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

[kac2]

it seems as if I can't fully remove the Compaq agents from the machine. I've tried absolutely everything from the device manager to add/remove hardware and software.

Whenever I remove the agents from the Device Manager, they re-appear on the next boot. If I set them to just be disabled, then I get errors on booting up.

Any ideas?

[jayolsen]

Could try booting into safe mode and then removing.

[NTurnbull]

Hi, what do you see if you browse the registry to HKLM\System\Current Control Set\Services\Tcpip\Parameters\Interfaces ? Also had a problem after a p2v and had to disable the virtual adaptor, boot, remove all adaptors inc hidden, reboot, check the above reg key and make sure that there are no adaptors listed, shutdown, enable the virtual nic and then restart..

Thanks,

Neil

[kac2]

i tried booting into safe mode and the same thing happens. I delete the non-plug and play devices and then they reapper.

I also removed the virual NIC. booted. removed all the interfaces from the registry. re-added the virtual nic. and still no network connectivity. I am getting an error now when i do 'ipconfig /renew', it says "Error: No adapters bound to TCP/IP are enabled for DHCP"

This is what I have in my device Manager

Network Adapters

- Direct Parallell

-RAS Async Adapter (cannot delete, needed for boot)

-Vmware Accelerate AMD PCNet Adapter

-WAN Miniport (IP)

-WAN Miniport (L2TP)

-WAN Miniport (PPTP)

Non-Plug and Play Drivers

-.Net Runtime Optimization Service v2.0.50215_x86 (grayed out)

-Adobe Workflow Server (grayed out)

-adpu160m

-AFD Networking Support Environment

-Beep

-cpq32fs2 (disabled and reappers on uninstall)

-Cpqarray (disabled and reappers on uninstall)

-cpqarray2 (disabled and reappers on uninstall)

-cpqcissm (disabled and reappers on uninstall)

-Disperf

-dmboot

-dmload

-EraserUtilDrv17 (grayed out)

-EraserUtilRebootDrv ((disabled)

-ESUG Remote Service (grayed out)

-Fips

-Fs_Rec (grayedout )

-Generic Packet Classifier

-Gernuaw (grayed out)

-IPSEC Driver

-KSecDD

-Microsoft .Net Framework v1.1.4322 update (grayed out)

-mnmdd

-mountmgr

-NAVAP (grayed out)

-NAVAPEL (grayed out)

-NAVENG

-NAVEX15

-NDIS System Driver

-NDProxy

-NetBios over Tcpip

- NetDetect

-Null

-partmgr

-ParVdm

-pcAnywhere Hose Service (grayed out)

-pcAnywhere Install Service (grayed out)

-PCIIde

-PlateSpin Remote Execution Service from gdmrsa1.greenebaum.com (grayed out)

-PlateSpin Remote Execution Serivce from inmage-tgt-.greenebaum.com (grayed out)

-RPDWD

-Remote Access Auto Connection Driver

-Remote Access IP ARP Driver

-SAVRT

-SAVRTPEL

-SPBBCDrv

-Special Purpose Utility Driver

-sym)hi

-Symantec Antivirus Client (grayed out)

-Symantec Eraser Control Driver

-symc810

-symc8xx

-SymEvent

-SYMREDRV (grayed out)

-SYMTDI (grayed out)

-Sync Driver

-TCP/IP Protocol Driver

-TDTCP

-Terminal Device Driver

-Total Network Inventory Service Helper (grayed out)

-vga (grayed out)

-VgaSave

-VMWare Server memory controller

-VPRemote Instal Bootstrap Service (grayed out)

-Vstor2 converter virual storage

-Windows Service Pack Installer Update service (grayed out)

I guess I am just going to go through the registry and delete everything that is HP or Compaq related.

[hjollis]

Hi

What I would do is to remove any network adapter from the vm

Uninstall any hp networking software if it (tool to build teams)

Go to the registry find the ip of your old network connection in hklm\system\controlsset\Services\[guid of network adapter]\parameters\tcpip

take the guid of the network adapter and search for it in the registry , and delete all the keys that you find.

then add new adapter to the vm

This Has worked for me on p2v machines with networking problems.

with regards

Hjölli

[kac2]

I've tried every possible combination to get this working. I've deleted Compaq agents, HP NIC teaming, removed the old nics from device manager, ran Slickbag's scripts, deleted registry keys, and I still can't pull an IP address.

When i do an ipconfig /renew i recieve:

Windows 2000 IP Configuration

The following error occurred when renewing adapter Local Area Connection 3: An internal error occurred. Disconnect and reconnect the network interface or reboot the machine.

I think this machine just might be a lost cause.

[RParker]

Did you try reparing the winsock?

1. Go to Start>Run, type in: netsh int ip reset c:\resetlog.txt

2. Restart your computer and you're done.

3. Follow the steps below if you have XP SP2 (this only works on windows XP SP2 and later).

4. Go to regedit.

5. Go to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services

6. Click on Winsock and Delete.

7. Click on Winsock2 and Delete.

8. Close registry.

9. Restart your computer

10. Go to properties of Local Area Connection

11. Click on the Install button in the Properties window

12. Choose PROTOCOL, then click on ADD button.

13. Click on HAVE DISK button...

14. Type in C:\windows\inf\nettcpip.inf in the dialog box and click OK.

15. Choose from the list INTERNET PROTOCOL TCP/IP in the list, and click OK.

16. Click CLOSE.

17. Reboot your computer.(At this point the Winsock is complete however
    to not only prevent this problem from happening in the future but also
    to make the process a lot easier you should update Windows.)

Try these steps: http://support.microsoft.com/kb/837333

[kac2]

this is a Windows 2000 Advanced Server box.

whe i run the command i get:

The Following command was not found: int ip reset c:\resetlog.txt

[kac2]

Following the steps from this article did it!!! YAAA!!

To repair

network or modem connectivity issues, follow these steps:

1. Remove TCP/IP.

2. Delete the Bind registry value, the Tcpip subkey, the Winsock subkey, and the WinSock2 subkey.

3. Reinstall TCP/IP.

Step 1: Remove TCP/IP

loadTOCNode(2, 'moreinformation');

Remove TCP/IP for the local area connection. To do this, follow these steps.

Note Before you remove TCP/IP, make a note of the IP and the DNS settings.

1. Click Start, point to Settings, and then click Network and Dial-up Connections.

2. Right-click Local Area Connection, and then click Properties.

3. In the Components checked are used by this connection list, click Internet Protocol (TCP/IP).

4. Click Uninstall, and then in the Uninstall Internet Protocol (TCP/IP) dialog box, click Yes.

5. When you are prompted to restart your computer, click Yes.

Step 2: Delete the Bind registry value, the Tcpip subkey, the Winsock subkey, and the WinSock2 subkey

loadTOCNode(2, 'moreinformation');

To delete the Bind registry value, follow these steps.Important

This section, method, or task contains steps that tell you how to

modify the registry. However, serious problems might occur if you

modify the registry incorrectly. Therefore, make sure that you follow

these steps carefully. For added protection, back up the registry

before you modify it. Then, you can restore the registry if a problem

occurs. For more information about how to back up and restore the

registry, click the following article number to view the article in the

Microsoft Knowledge Base: 322756

(

)

How to back up and restore the registry in Windows

1. Click Start, click Run, type regedit in the Open box, and then click OK.

2. In the left pane, expand HKEY_LOCAL_MACHINE, and then expand SYSTEM.

3. Expand CurrentControlSet, and then expand Services.

4. Expand lanmanserver, and then click Linkage.

5. In the right pane, right-click Bind, and then click Delete.

6. In the Confirm Value Delete dialog box, click Yes.

7. Expand lanmanworkstation, and then click Linkage.

8. In the right pane, right-click Bind, and then click Delete.

9. In the Confirm Value Delete dialog box, click Yes.

To delete the Tcpip, the Winsock, and the WinSock2 registry subkeys, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.

2. In the left pane, expand HKEY_LOCAL_MACHINE, and then expand SYSTEM.

3. Expand CurrentControlSet, and then expand Services.

4. Right-click Tcpip, click Delete, and then in the Confirm Key Delete dialog box, click Yes.

5. Right-click Winsock, click Delete, and then in the Confirm Key Delete dialog box, click Yes.

6. Right-click WinSock2, click Delete, and then in the Confirm Key Delete dialog box, click Yes.

7. Restart your computer.

Step 3: Reinstall TCP/IP

loadTOCNode(2, 'moreinformation');

Reinstall TCP/IP back to the local area connection that you removed it from. To do this, follow these steps:

1. Click Start, point to Settings, and then click Network and Dial-up Connections.

2. Right-click Local Area Connection, and then click Properties.

3. Click Install, click Protocol in the Click the type of network component you want to install list, and then click Add.

4. In the Network Protocol list, click Internet Protocol (TCP/IP), and then click OK.
   
   Note Replace the IP and the DNS settings with the values that you made note of at the beginning of the "Remove TCP/IP section."

Thanks for the help everyone!!

[joemath]

kac2,

Thanks for posting your solution.

I encountered similar networking issues this weekend while trying to virtualize a Win2k Pro SP4 machine. KB837333 fixed the problem.

--Joe

[Eldron01]

kac2,

Thank you very much for sharing this find. It saved me a lot of time.

[thetootall]

I had a similar experience this weekend - performed a P2V of 2 Compaq servers, both Windows 2000 server. I make sure before the P2V process to remove all of the Compaq/HP software and services yet there still seemed to be some remnants left over even with everything looked clear. The Microsoft KB definitely did the trick - thanks for your persistence to find a resolution and more importantly post what the fix was!

[klsitton]

I have the issue, but this procedure has not alleviated it.  I have reinstalled VMWare Tools, reinstalled the network device, deleted and reinstalled the TCP/IP protocol and registry keys several times, but cannot get connectivity.  I can ping other VMs I have running, and ping the host gateway, but still no internet connectivity beyond the host.

Any suggestions?

[Scott Vessey]

Start your own thread rather than resurrect one that was last active 12 years ago?

 

[klsitton]

Sure, I can do that.  I just wanted the history.