Q:
Firewall error after deleting Terminal Server service
IPNAT.SYS, NAT conflict, Firewalls, Windows Server 2003, Windows firewall, SonicWALL, Terminal Server, Windows Server 2003 administration, VPN, Internet Connection Sharing One of my customers is getting a strange error since someone disabled (deleted actually!!) the Terminal Server service on their Windows 2003 Server SP1.
The error that pops up is: "Windows Firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys)", and the VPN clients can't access the LAN anymore.
I have Googled this error and all answers seem to point to a NAT conflict with the Windows Firewall or the Internet Connection Sharing. However they do NOT have the Windows Firewall or the Internet Connection Sharing enabled.
Microsoft Support website solutions either related only to WinXP or to VPN clients connecting via IIS, which is not the case here (they are SonicWall VPN clients connecting into a SonicWall box). The closest article I've found is: http://support.microsoft.com/?kbid=897651 but it doesn't quite apply here.
Any ideas what this could be and/or where I could get more info?
Many thanks in advanced,
The error that pops up is: "Windows Firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys)", and the VPN clients can't access the LAN anymore.
I have Googled this error and all answers seem to point to a NAT conflict with the Windows Firewall or the Internet Connection Sharing. However they do NOT have the Windows Firewall or the Internet Connection Sharing enabled.
Microsoft Support website solutions either related only to WinXP or to VPN clients connecting via IIS, which is not the case here (they are SonicWall VPN clients connecting into a SonicWall box). The closest article I've found is: http://support.microsoft.com/?kbid=897651 but it doesn't quite apply here.
Any ideas what this could be and/or where I could get more info?
Many thanks in advanced,
ASKED:
Feb 26 2009 9:40 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
A:
RATE THIS ANSWER
0
Click to Vote:
0
Click to Vote:
- 0
0
So you are trying to access this WinServer2003 Terminal Server from a remote location(Outside your local network)?
The question is that are other users trying to access Terminal Server within the Private Network via VPN having the same problem?
You can enable the Terminal Server services on WinServer2003.
Follow these steps to enable Terminal services on WinServer 2003:
1) Start---->Settings--->Control Panel----> Add/Remove Program---->Windows Component--->Terminal Server.
After enabling Terminal Services on WinServer 2003, check and see if the problem is resolved.
I hope this helps
