Changed IP of guests, now not working


i changed ip of 4 guest machines in preparation moving primary hyper v server brand office.  turned on server , none of guests can see network.

 

the primary server can.  server has 4 nic's.  configured

hyper v - local area connection 1

2 guests lac 2

1 guest lac 3

1 guest lac4

i changed ip inside os of each guest, not on hyper v.

i notice hyper v has 3 virtual adapters set dhcp , getting leases new office, right?  didn't pay attention adapters on hyper v server when built it, because worked.

so example, lac 4 on hyper v machine getting ip of 192.168.75.51 (the dhcp scope there 75.50- 75.150

and in server using lac 4, programmed use 192.168.75.14, static , inside same /24 route , should work, can anywhere.

 

what happened after re-ip ing guests machines , host server, then sending host server down new office, networking setup didn't work.

 

it straight forward... 192.168.75.x /24

host .11

guest .4

guest .12

guest .13

guest .14

 

i tore down entire physical , virtual networking components , started scratch.  still nothing.  happened upon article mentioned mac filtering, , port security on cisco switches.  there brand new model switch down there.  network admin checked settings , found locked ports, , unlocked them , turned off security features , came back.

 

i re-ip's , good.


way, 1 thing ended not being issue, i'm curious about, 3 phycisal nics because virtual nics, physical side turned in virtual protocol nics only, , 3 new virtual nics showed up.  sounds pretty normal, when looked @ new virtual nics on host machine, setup v4 dhcp, nic set if don't mess right?  don't understand why.  taking 3 dhcp ip's seem unnecessary.  checked again , 1 of them show in ipconfig /all still don't understand why it's there.

 

ethernet adapter local area connection 6:

   connection-specific dns suffix  . :
   description . . . . . . . . . . . : local area connection 3
   physical address. . . . . . . . . : 78-2b-cb-1c-6f-6f
   dhcp enabled. . . . . . . . . . . : yes
   autoconfiguration enabled . . . . : yes
   ipv4 address. . . . . . . . . . . : 192.168.75.58(preferred)
   subnet mask . . . . . . . . . . . : 255.255.255.0
   lease obtained. . . . . . . . . . : sunday, june 19, 2011 2:43:33 pm
   lease expires . . . . . . . . . . : monday, june 20, 2011 11:43:33 am
   default gateway . . . . . . . . . : 192.168.75.1
   dhcp server . . . . . . . . . . . : 192.168.75.1
   dns servers . . . . . . . . . . . : 192.168.75.4
                                       192.168.40.2
   primary wins server . . . . . . . : 192.168.40.83
   netbios on tcpip. . . . . . . . : enabled

 

 



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file