Windows Server 2012 R2 periodically unreachable yet services still available


hello,

our shop installed dozen winserver 2012 r2 servers couple weeks ago. week, have notices odd behaviors reported our networking monitoring tool (solarwinds). @ random times of day, servers icmp unreachable. aside looking @ mt solarwinds console, try manually ping these servers , confirm cannot. yet, example, our "home drive" file server supposedly looses connectivity, yet still mapped , able browse documents; same goes desktops items.

there 1 occasion did loose our resources (home drive, desktop) when happened.

the weird issue connectivity restored after 4-7 minutes. during outage time, cannot ping or rdp servers.

we have looked @ event logs , hbss logs , nothing far reveals error caused issue.

also, not happen @ same time, they're "unreachable" 1 or 2 @ time.

this stumping me, advice appreciated.

are pinging name or address? 'destination host unreachable' have couple different meanings.

this message indicates 1 of 2 problems: either local system has no route desired destination, or remote router reports has no route destination. 2 problems can distinguished form of message. if message "destination host unreachable," there no route local system, , packets sent never put on wire. use route utility check local routing table.

if message "reply < ip address> : destination host unreachable," routing problem occurred @ remote router, address indicated "< ip address> " field. use appropriate utility or facility check ip routing table of router assigned ip address of < ip address> .

 https://technet.microsoft.com/en-us/library/cc940095.aspx

 

 


regards, dave patrick ....
microsoft certified professional
microsoft mvp [windows]

disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.



Windows Server  >  Windows Server 2012 General



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file