[Klaus]

Sorry, this can take a while. I can access the system via serial port but it can't see the world.

[Guest]

time to bookmark the forum here then, that's still accessible.

[Klaus]

Ok, I used my magic hands in combination with a series of blasphemic outcrys.



If your Win-network is suddenly down for no reason - maybe try this ...



[color="#222222"][size="2"]netsh interface set interface "interface name" DISABLED[/size][/color]

[color="#222222"][size="2"]+[/size][/color]

[color="#222222"][size="2"]netsh interface set interface [/size][/color][color="#222222"][size="2"]"interface name"[/size][/color] [color="#222222"][size="2"]ENABLED[/size][/color]

[size="2"] [/size]

[color="#222222"][size="2"]GAAAAAAAAAAAAAAAAHHHHHHHHHHHHHHHHH!!!! [/size][/color]

[color="#222222"] [/color]

[color="#222222"] [/color]

[miro]

It is not only MS problem,

While in windows you have to do



netsh interface ip reset C:\resetlog.txt



In lunux you have to do something like ....



sudo /etc/init.d/networking restart







Phhh there are somo many linux distros and they all differs a little bit.



The most important question why the IP stack was disabled/trown on wrong state. The logging could help in this case. Just to prevent the next unexpected shutdown