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

VMWare player uninstalled but giving IP address conflict

HI,

I installed VMWare player and created a virtual machine e.g. 'abc'. then after using for few days I deleted it and uninstalled VMWAre player. Later I installed a physical machine with the same name of virtual machine e.g.'abc' but its showing IP conflict and there is no IP matching with each other (I check in DSL router) and the only thing similar look is the same name as virtual machine was having. I have noticed whenever I ON the machine which was hosting virtual machines starts giving IP conflict on newly installed physical machine.

Any idea? even VMWare player is uninstalled.
0
baberamin
Asked:
baberamin
  • 14
  • 11
15 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Can you check your network and ping the conflicting IP address with another PC on the network?

in the event log, does it give an error and a MAC address?
0
 
coolsport00Commented:
Your DHCP server might have this as still 'leased' out.

~coolsport00
0
 
baberaminAuthor Commented:
I can see my routher is showing some devices as

dsldevice  0.0.0.0
dsldevice  0.0.0.0
dsldevice  0.0.0.0
dsldevice  0.0.0.0

how to get rid?

Router is Thomson Gateway
0
Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
all zeros or ip addresses?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
turn it off or restart it.
0
 
baberaminAuthor Commented:
ip addresses are there for actual machines running but all zeros are also there dont know for what?
I deleted them manually and restarted router but still there.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, back to my original question. In the event log of the Windows machine, can you post the event log entry.

can you ping thr offending IP address from a computer on your network.

can you provide the MAC address of the offending machine?

after pinging it look in your ARP cache with arp -a
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
on the computer that hosted had vmplayer installed check your network interfaces you have installed, its possible that vmware player has not removed the virtual network interfaces it installed.

so what nics and ip addresses do you have on the host?
0
 
baberaminAuthor Commented:
Hi,

entry from Event log
"
The system detected an address conflict for IP address 192.168.1.90 with the system having network hardware address 00:26:C7:F2:61:78. Network operations on this system may be disrupted as a result.
"

yes I can ping it and it gives me machine name "machinename.lan" but that machine is only having name "machinename" and not "machinename.lan" from where its getting .lan?

arp -a showing me a list but in that I cannot see 00:26:C7:F2:61:78

when I do ipconfig /all on my machine where vmware was installed its shows me extra connections with * and media disabled. I removed some Network apaptors like
nata**.lan and .lan{***}
and something psedao (I may not be able to write exact spellings as I remember them little)

but when I restart this machine .lan adaptors again occurs.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That MAC address belongs to a Intel Network card.

Virtual Machine MAC addresses are often 00:50:56 or 00:05:69

what is the Mac address of your computer?

you can find from ipconfig /all
0
 
baberaminAuthor Commented:
which computer?
which was having VM player installed?  (anyhow its **-**-**-**-76-BD)    ok lets call it from now M1
or the one which I installed recently with the same name a VM was having? (**-**-**-**-83-6A)  and call it M2

0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
so you have IP address 192.168.1.90 statically or dhcp assigned to computer M1.

which computer M1 or M2 gives the IP address conflict?

are they all set for DHCP?
0
 
baberaminAuthor Commented:
DHCP.
M1 ip 192.168.1.67
M2 ip 192.168.1.90

M2 give IP conflict. M2 is a physical machine now previously it was a virtual Machine on M1. On M1 VM player was installed and later uninstalled and I bought a physical machine for M2 now.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
and with M2 turned off, you can ping 192.168.1.90 from 192.168.1.67?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
check the TCP/IP settings on M1, there is no static IP setup?
0
 
baberaminAuthor Commented:
one interesting thing when M2 is OFF and I try to ping 192.168.1.90 its give following:

ping 192.168.1.90

Pinging 192.168.1.90 with 32 bytes of data:
Reply from 192.168.1.67: Destination host unreachable.
Reply from 192.168.1.67: Destination host unreachable.
Reply from 192.168.1.67: Destination host unreachable.
Reply from 192.168.1.67: Destination host unreachable.

Ping statistics for 192.168.1.90:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),


any idea i'm pinging .90 but saying .67 not reachable?


should I give try by installing vmplayeragain on M1 and create vm M2 and rename as M2-123.
May be that solve issue?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
it's unreachable because 192.168.1.90 is not on, or responding from the computer which you are using which is 192.168.1.67.

so there is nothing currently on your network (maybe), that has the IP address 192.168.1.90.

you could prove this by giving the IP address statically to M1, so assign M1 the IP address 192.168.1.90

does it complain on an IP address conflict when powered up?
0
 
baberaminAuthor Commented:
I assigned the IP of M2 to M1 by making M1 static and M2 now got IP address 192.168.1.70 as its still dynamic and now its saying in event viewer

The system detected an address conflict for IP address 192.168.1.70 with the system having network hardware address 00:22:5F:25:7D:67.


I want to share one surprising thing that whenever M2 restarts its showing confilicting mac address different as shown below from event viewer before changing ip when it was having 192.168.1.90.

The system detected an address conflict for IP address 192.168.1.90 with the system having network hardware address 00:16:D4:F0:9B:32.

after restart

The system detected an address conflict for IP address 192.168.1.90 with the system having network hardware address 00:1F:3A:35:93:C1.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
well that's weird.

you've got three devices on your networking that are conflicting

00:22:5F:25:7D:67
00:16:D4:F0:9B:32
00:1F:3A:35:93:C1

is this a wireless router?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
can you screen shot your networking connections?
0
 
baberaminAuthor Commented:
yes,
its wireless router.
I'll send u screen shot later.
0
 
baberaminAuthor Commented:
can anyone tell me what is this isatap?
please see the attached screen shot. isatap screen shot- network adaptors section
0
 
baberaminAuthor Commented:
the above screen shot is from M1
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
could you screen shot the network connections in Networking, these are under Device Manager.

also could you provide output from ipconfig /all on ALL computers.

and also provide output from DHCP on your router. Please leave IP addresses and MAC Addresses.
0
 
baberaminAuthor Commented:
Hi,

I disabled the network card and installed USB Wirelss network point and problem resolved.

I was thinking it may be related to VMWare player but now its proved it was the fault of network card. I was tired of this problem because conflicting mac address I was not able to find anywhere and another surprising thing that on M2 arp -a after restarting the server was showing a very long list of Ips and mac addresses I dont know from it was getting.

anyhow thanks to all who helped me to resolve it.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
glad you git it working
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

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