Link to home
Start Free TrialLog in
Avatar of jamesmonilaws
jamesmonilaws

asked on

ipnat - Server 2003 (SBS) Stop all in bound connections to server

SBS Server 2003 which on reboot accepts no inbound connections, client logins, pings, shared folder  access, exchange connections etc (It is a virtual server so using viewer I can access the server and see that in all other respects working fine.)

I found a hint whihc suggested ipnat.sys can cause this problem, suggesting it was used by pc- anywhere which happens to be on this server. Removing pcaw dis not fix.

However, normal service can be resumed by entering the command "sc stop ipnat"

other suggestions implied RRAS coudl cause this if it had firwall enabled. Reconfigured rras to verify no firewall function enabled.

The problem occured after removing sophos enterprise 5.0.2 from the server, but this may be a coincidence. (I have called sophos support on the subject, they seemed to think the un install had worked fine, and had not seen anything similar.)

So to date the only way to get this server to operate normal after a reboot is to stop ipnat per above.

Ideas?
ASKER CERTIFIED SOLUTION
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jamesmonilaws
jamesmonilaws

ASKER

Have just applied the suggested reserved ports. Cannot restart for another 3-4hours. Will advise outcome.

(strangely, I just had to put an entry in the registry entry referred to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
, which was empty prior, for blackberry services on port 3101. Although everything worked fine after that change.)

thanks for the suggestion.
No problems - you may find the IPSEC Services Service set to Automatic but not started - it should be set this way, so please make sure it is (before you reboot) and once the server is rebooted, this service should start and then you should be fine.

It is a common SBS 2003 problem (sadly).

Alan
Did the job first time. I installed all of the suggested reserved ports.. The KB article did not directly refer to the reported issue, but the fix certainly solved the problem
Alan thans for a speedy response and solution
Excellent news - glad it resolved your issues (which I knew it would ;) )

Thanks for the points.

Alan