I have a bit of a weird issue. I have a HyperV server (192.168.0.3) that hosts all my VM's in my network and, up until today, I have had no issues with it.
Now for some reason the PC that is hosting the VM's can not communicate outside of its own subnet....
All other machines on the subnet have no issues, and all the VM's function fine.
There is a central router that handles all my cross subnet routing and internet routing (192.168.*.10 on all subnets). Both the router and the HyperV machine work on the same switch.
My VM's run on both my workstation VLAN/SUBNET (192.168.0.0/24) and on a VM only subnets (192.168.100.0/24 192.168.101/24)
There has been no power or internet loss at the location that hosts the server hardware, the HyperV server simply stopped communicating with anything outside the 192.168.0.0/24 subnet.
A tracert to my RAS server stops at the router (192.168.0.10) and goes no further, all pings to and from any other subnets just time out.
ROUTE PRINT
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.10 192.168.0.3 261
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.0.0 255.255.255.0 On-link 192.168.0.3 261
192.168.0.3 255.255.255.255 On-link 192.168.0.3 261
192.168.0.255 255.255.255.255 On-link 192.168.0.3 261
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.0.3 261
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.0.3 261
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.0.10 Default
LOGS FROM ROUTER
Mar 16 15:28:08 EXGA-FIREWALL-001 kernel: IPv4: martian source 192.168.0.3 from 0.0.0.0, on dev eth0
Mar 16 15:28:08 EXGA-FIREWALL-001 kernel: ll header: 00000000: 01 00 5e 00 00 01 e0 b9 e5 99 40 5e 08 00 ..^.......@^..
No comments:
Post a Comment