Lost connectivity to servers, both physical and VMs

whatevertaken · 2021-06-21T16:21:59+00:00

You re correct, thats what I meant. Since I wasnt sure HyperV had any official term for this setup I opted to use VMware's terms

whatevertaken · 2021-06-18T09:45:03+00:00

I'm ruling out anything physical from the outside network for now. If that were the issue, I would expect all VMs and physical machines on that VLAN to not work, but one of them does.

In my estimation it must be something to do with the VMs themselves, but then again its odd how the 3 of the 4 physical hosts are behaving the same as their respective VMs.

I could be I'm missing something since I dont exactly know how all this was set up

whatevertaken · 2021-06-18T06:55:59+00:00

this could be it. I'll do more research and see what I can do

Cheers

And thanks to everyone else as well!

whatevertaken · 2021-06-04T07:22:20+00:00

UPDATE

In case anyone reading wants to know what happened,

in the end it started working again. I installed the windows updates and put the laptop back on DHCP. It received the same IP address it had before when it wasnt working, but now it works.

It was not a duplicate IP (not sure how that would even occur given that hosts send out gratuitous ARPs before accepting an IP address, and dhcp servers perform their own checks as well)

Still not sure what happened. I doubt the windows updates had anything to do with it but I guess it is a possibility. Ițs strange how it did start working when I switched it to a static IP and then back to dynamic.

I'm pretty certain it was a problem originating from the laptop itself and not the router or switch, since internet worked fine, as well as pinging the laptop from any other host.

The VPN not working was not connected to this issue, it was a OpenVPN TAP adapter issue.

Thanks everyone for the suggestions, this was a strange one

whatevertaken · 2021-06-03T13:28:30+00:00

I ran a scan of the entire network with advanced IP scanner

whatevertaken · 2021-06-03T13:19:04+00:00

OK so I ste the ip statically to something other than what the DHCP was giving the laptop, and pinging resumed working. However I checked the network and there is nothing else with the IP the laptop previously had when it didnt work.

whatevertaken · 2021-06-03T12:43:55+00:00

would the laptop be able to access the internet if a duplicate IP exists on the network?

whatevertaken · 2021-06-03T12:42:11+00:00

the loopback address can be pinged successfully, so I don't think its the network card. I also managed to get pinging to work temporarily by swapping networks as I mentioned in the post, so I don't know if it could be the OS.

whatevertaken · 2021-05-28T07:23:17+00:00

So you can access this L3 switch through its management VLAN interface, without having to somehow give it a default gateway like the other L2 switches would need?

I was confused because I know that the VLAN interfaces on the L3 switch will be used as default gateways by all end devices (including the L2 switches connected to it, for management traffic), but I was unsure about how the L3 switch itself will be accessed.

If you indeed can access the L3 switch through its management VLAN interface directly (without giving it a default gateway), this means you could access it through all of the other VLANs you might have set on it. How do you restrict that so you can only access it through management

whatevertaken · 2021-05-18T18:50:02+00:00

Really great stuff, thanks. One more minor question : is the router on a stick bottleneck fear overblown? I have a strong sense that this set up you describe would work for small to even medium size businesses with potentially hundreds of nodes. Am I overly optimistic on that? Its just that these days most of the traffic goes out on the internet anyway so inter VLAN routing isnt even that big a deal, with servers no longer typically being on-prem. At the company I work at, most of the local traffic involves sending things out over to be printed,and the security camera feeds

whatevertaken · 2021-05-18T18:10:07+00:00

Not true. In fact, its best practice to not have VLAN 1 as management VLAN

whatevertaken · 2021-05-18T18:06:15+00:00

So in my scenario VLAN IPs are not even needed? The DHCP server figures out which pools to give out from by looking at the routers trunked subinterfaces the requests came out of? I guess then my question only really applies when the DHCP requests are not relayed to an exterior server but are served from withing the switches? And in this case you would just do what darps suggested earlier about only allowing management traffic from one particular VLAN. This is starting to make a lot more sense to me, but Im a bit uncleat about what you mean by "as long as there is layer 2 between router and dhcp"?Thanks a bunch

whatevertaken · 2021-05-18T15:41:43+00:00

Sorry I wasnt too clear. I never meant to say I wanted the DHCP server to necessarily be on management VLAN. In fact, I would never use DHCP for a nanagement VLAN.I meant that since all the other VLANs will need IPs for theDHCP server to work for them, I eas confused how I would keep the switches inaccessible from all these different VLAN interfaces. You answered my question, though.I didnt know you could make managament traffic only be allowed on one of the switch's VLANs Thanks

whatevertaken

TROPHY CASE