ICS problem

[Guest]

Scenario is that I have two PC's, both at XP SP2, connected via an adhoc
wireless network. One PC has a dial-up internet connection which is setup to
be shared over the wireless network.

The problem is that I have fine connectivity between the PC's (file sharing,
etc); I can initiate a dialup session from the client PC; I can then ping web
addresses from the client PC; Windows Update can quite happily download from
the client PC; but I am not able to get a browser session to work.

All firewalls are disabled and no strange proxy settings are in place.

I'm a bit flummoxed - anyone any ideas?

 

[Steve Winograd [MVP]]

Scenario is that I have two PC's, both at XP SP2, connected via an adhoc
wireless network. One PC has a dial-up internet connection which is setup to
be shared over the wireless network.

The problem is that I have fine connectivity between the PC's (file sharing,
etc); I can initiate a dialup session from the client PC; I can then ping web
addresses from the client PC; Windows Update can quite happily download from
the client PC; but I am not able to get a browser session to work.

All firewalls are disabled and no strange proxy settings are in place.

I'm a bit flummoxed - anyone any ideas?

These tests should help find the problem:

1. On the host computer, right click the local area network connection
and click Status | Support | Details. It should show:

IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway: none
DNS Server = none

2. On the client computer, right click the local area network
connection and click Status | Support | Details. It should show:

IP Address: 192.168.0.x (1<x<255)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Server = 192.168.0.1

3. If #1 and #2 are right, open a command prompt window on the client
and enter these lines. Each one should get four replies:

ping 192.168.0.1
ping 216.239.39.99
ping google.com

4. If #1-#3 are right, enter these addresses in Internet Explorer.
They should both take you to the Google web page:

http://216.239.39.99
http://google.com

If the only failures are the Google tests in #3 and #4, the client's
DNS server setting is wrong.

Otherwise, it could be an MTU problem. In that case,

1. Find the right MTU setting on the client, as shown here:

http://www.annoyances.org/exec/show/article04-107

2. Make the setting manually on the client, or use DrTCP to make it:

http://www.dslreports.com/front/drtcp.html
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com