Hey,
I have 2 computers, running Windows XP Pro (not SP2). The first computer has 2 lan cards, the second has one. One of these is connected to the internet (IP ). The other lan card is connected to the second computer using a network crossover cable. The IP of the second lan card on the first computer is set to and the IP of the second computer is

The problem is that though the two computers can see each other on the network, share files and ping each other, only the first computer can access the internet. The second cannot access the internet. I have ICS running on the internet computer. The second computer has detected that there's an internet connection through the first computer and network connections shows that there is an internet gateway through the first computer. Despite that, it can't access the internet. Both computers can share files. Can anyone help me out please?

Dani AI

Generated

Quick, practical checklist for (and thanks to for the Network Wizard tip). Since the wizard didn’t fix it, focus on a few ICS-specific traps that commonly leave the client able to see the host but not reach the Internet.

Make sure ICS is enabled on the Internet-facing adapter and that the internal (crossover) NIC is selected as the “home”/private interface — when ICS is turned on Windows will act as a DHCP/NAT/DNS gateway for the LAN and normally sets the host’s internal adapter to the 192.168.0.1 network. Clients should be set to obtain IP and DNS automatically (or, if you insist on a static client IP, set the Default Gateway and DNS to the ICS host). [Microsoft: Set up Internet connection sharing]. (learn.microsoft.com)

Run simple isolation tests to see whether the problem is routing vs. DNS vs. firewall. On the host confirm the Internet works; on the client check what it actually has:

ipconfig /all
ping 192.168.0.1
ping 8.8.8.8
nslookup www.google.com

If the client can ping 8.8.8.8 but cannot resolve names, it’s DNS. If it can’t ping an external IP at all, the host isn’t forwarding/NATting or a firewall is blocking. If host browsing works but client fails, that narrows it to ICS/config or filtering on the host.

Check services and firewalls: the Windows Firewall/Internet Connection Sharing (SharedAccess) service must be present and functioning and third‑party firewalls or other sharing software can break ICS. Also don’t mix ICS with a Network Bridge — they conflict. If your host uses an authenticated web proxy or you’re on a corporate 10.x network that blocks NAT, ICS won’t transparently forward proxy credentials; in that case either configure the clients to use the proxy or run a local proxy on the host (or use a small hardware router). [Microsoft: ICS/ICF docs]. (learn.microsoft.com)

If the above checks don’t find the fault: disable any third‑party firewall temporarily, restart the SharedAccess service, re-run the tests, and consider trying a cheap hardware NAT router between the ISP network and your two PCs — it will usually resolve odd ISP/corporate policy and NAT issues faster than fiddling with ICS.

Recommended Answers

All 2 Replies

Hey
I would suggest that you should run windows network wizard.
It would solve this problem. run it on both computers and follow the instructions.

I tried that. No avail. Any other suggestions?

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.