Vlan unstable in vm's after "new config"


Recommended Posts

Hi all,

 

I have a very weird problem... after I removed some drives and used the "new config" option my vm's seems to lose connection every few seconds with internet and lan.

 

When I ping the servers I get this:

 

Reply from 172.254.254.12: bytes=32 time=1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Request timed out.
Request timed out.
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Request timed out.
Request timed out.
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63
Reply from 172.254.254.12: bytes=32 time<1ms TTL=63

Does anyone know what the problem might be?

unraidserver-diagnostics-20200617-2100.zip

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.