Member Avatar for INET

I have installed SP1 available for windows xp 2003 server (already installed and working having Lan and domain settings) after SP1 installation internet sharing stops on all domain users. i tried best to solve the problem even reinstall the server and set domain again. plz tell me its solution. most of other people have same problem in there setup. looking for some solution thanx.

  • 3 Contributors
  • 2 Replies
  • 189 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by chicagotech

Dani AI

Generated

Short summary and what to try next (quick checklist)

— SP1 can change how the server’s NAT/firewall stack behaves, so the symptom you describe (clients lose Internet after SP1) is common. ’s pointer to the official docs and ’s suggestion to use NAT are both sensible. Below are focused, practical checks and a safe short plan you can follow right away.

Immediate checks (do these on the server)

sc query sharedaccess        # check ICS service
sc query remoteaccess        # check RRAS service
net start sharedaccess       # start ICS if stopped
net stop remoteaccess        # stop RRAS to test for conflicts

Why this helps: ICS is provided by the SharedAccess service and will conflict with Routing and Remote Access (RRAS) or other NAT software (ipnat.sys). ICS also implicitly provides DHCP/DNS for the LAN — that conflicts with a domain controller’s DNS/DHCP if the server is a DC.

Short action plan

  • Verify which NIC is external vs internal and that ICS (or NAT) is bound to the external NIC.
  • If RRAS is installed and you see firewall errors mentioning ipnat.sys or the firewall won’t start, stop RRAS and test ICS — or better, configure NAT using RRAS (recommended for servers).
  • If the server is a domain controller, do not run ICS for a production domain: ICS hands out addresses and overrides DNS/gateway behavior; use RRAS NAT or a dedicated router instead.
  • On a client, run ipconfig /all and confirm the gateway/DNS point to the intended host. Check the server System/Application event logs for SharedAccess/ipnat errors.

Short caution: ICS is intended for small, non-domain gateway scenarios. For any production/domain setup, use RRAS NAT or an edge router; that fixes the recurring SP1/ICS conflicts and is more stable.

Recommended Answers

All 2 Replies

Member Avatar for nanosani

See if this helps :

Member Avatar for chicagotech

You should use NAT istead of ICS. this page may help,

no ics after 2003 sp1
No ICS available after installing server 2003 SP1. Situation: after installing
Windows server 2003, there is ICS on the advanced tab of TCP/IP Properties. ...
&ics.htm - Similar pages

Microsoft Windows New release Issues
No ICS available after installing server 2003 SP1. Windows Firewall running on
DC - "Windows Firewall cannot run because another program or service is ...
www.howtonetworking.com/main.htm

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.