|
This morning we found the Windows 2003 server had rebooted and was now not accepting connections and not responding to ping on the network. The Server was online and we are able to connect via Team Viewer, also logging in locally from console was ok from all user accounts.. (Windows server 2003 R2 Standard Edition) The symptom was that the server did not accept any incoming network traffic. from within the same network . No response at all to any connections.
Opening the firewall settings would enable a popup message " Windows firewall cannot start because another program or service is running that might be using the Network Address Translation Component , IPNAT.SYS I have disabled Remote Access and Routing on the server, restarted and all systems are back online. I do not know why the Remote Access and Routing needed to be removed at this stage, it has been enabled since the server was built and now will have to look further into enabling and rectifying the issue. Remote access / VPN is still a requirement on the server.
|
|
|
|
|
|
A quick momentary fix was tried NET STOP IPNAT however after every reboot it happened again. A search on the net found another command.
|