• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1161
  • Last Modified:

Not able to ping local subnet after P2V conversion

Hi,

I have a really strange problem.
I have just converted a physical system to a virtual machine.
After this conversion I can successfully start the machine without any problems EXCEPT I can't ping any system in the same subnet, I can however ping everything behind the router...
Host: Microsoft Windows 2003 SP2
Virtual OS (ESX 3.5)
Virtual Ethernet Mode Bridging (in think, every host is using the same VMnic's)
On this ESX server I have 4 hosts running without any problems, the 5th one (the new one) can only ping to the internet or behind the router.  (other subnets connected via Lan-Lan VPN)
The IP adress of 5th the server is aquired via DHCP, and is in the range of the subnet 192.168.28.x, the router is on ipaddress 192.168.28.254.
I can't ping the firewall from this 5th server, but I can ping the internet, the other servers can ping the firewall and each other...
0
Filip Heens
Asked:
Filip Heens
1 Solution
 
Zaheer IqbalTechnical Assurance & ImplementationCommented:
Make sure the defualt gateway is the same of all devices..
0
 
Filip HeensAuthor Commented:
it is the same. already checked that
0
 
ryansotoCommented:
Are you pinging by name or IP?  Does neither work?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Filip HeensAuthor Commented:
neither work...
the DNS server is also in the same subnet...
all the other hosts work fine, and the Physical server (before the P2V) also works fine, it's just after the P2V and the creation of the new VMware NIC it fails to ping anything withing its own subnet...
One thing I did notice was that the first time I started the server he told met that there was a duplicate name on the network...
0
 
ryansotoCommented:
Is the physical still rolling?
0
 
Paul SolovyovskySenior IT AdvisorCommented:
Once you migrated via P2V did you clear the arp cache and dns cache since you're now using a different nic. Try deleting and re-adding the nic. Make sure the physical server is offline, if you bring it back on you can cause some issues with AD
0
 
philtpaikCommented:
Could be a long shot, but how many virtual port groups do you have? Have you set up anything outside of your firewall and internal subnet  such as a DMZ port group? Try checking the virtual switch to see what port groups you are on. Since you can ping something means that you do have connectivity. The fact that you cant ping inside of your firewall and the subnet inside, tells me the firewall is blocking you...which would mean you are outisde. If you havent already try checking.

In case you dont know...
Right click on VM
Edit Settings

check network settings.

0
 
Filip HeensAuthor Commented:
problem finally solved: i had a route to an old router that was still in place and somehow when changing to the new server it did work.
after I deleted the old persistent route everything worked fine
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now