ICS and Networking

[Gary]

I cannot network my computers using 192.168.0.1 configured on my host LAN
connection. ICS will work, though on the host and client..

If I configure 192.168.10.1 on the host and 192.168.10.x on the client
networking will work but ICS does not.

I understand I must use 192.168.0.1 on the host LAN connection for ICS to
work. Is this true?

Why can I not network using 192.168.0.x?

 

[Steve Winograd [MVP]]

I cannot network my computers using 192.168.0.1 configured on my host LAN
connection. ICS will work, though on the host and client..

If I configure 192.168.10.1 on the host and 192.168.10.x on the client
networking will work but ICS does not.

I understand I must use 192.168.0.1 on the host LAN connection for ICS to
work. Is this true?

Why can I not network using 192.168.0.x?

ICS only supports using 192.168.0.1 for the host's LAN connection.

192.168.0.x should work fine for networking. Since you didn't give us
any details of what goes wrong using those addresses, it's hard to say
what the problem is.

Permanently disable XP's built-in Internet Connection Firewall on the
LAN connection. Disable and un-install all other firewall programs
while troubleshooting.

If you'll post another news group message with complete details of the
problem, someone can probably help. Describe what works, what doesn't
work, troubleshooting steps that you've tried, complete text of all
error messages, etc.
--
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

 

[Mike Gigli]

Make sure that the gateway on your client is set to the
address of your host.

 

[Gary]

ICS only supports using 192.168.0.1 for the host's LAN connection.

192.168.0.x should work fine for networking. Since you didn't give us
any details of what goes wrong using those addresses, it's hard to say
what the problem is.

Permanently disable XP's built-in Internet Connection Firewall on the
LAN connection. Disable and un-install all other firewall programs
while troubleshooting.

If you'll post another news group message with complete details of the
problem, someone can probably help. Describe what works, what doesn't
work, troubleshooting steps that you've tried, complete text of all
error messages, etc.
--
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

Solution Delivered. It was a good one with a simple solution.

With SatDirect 3.0 the Networking with SatDirect pdf document instructs you
to configure your LAN connection with 191.168.10.x. This was done and all
was fine with ICS and networking. Following the SatDirect 3.0
installation I installed Norton Internet Securities 2003 on both machines
which it automatically configured 192.168.10.x as a trusted networking
connection within the firewall settings. With the SatDirect Plus
installation the 192.168.10.x settings were removed from both LAN
connections. This killed networking but ICS still worked. I worked though
Microsoft documents to get ICS to work (192.168.0.1 default in the Host LAN
and assigning IP automatically on the client) but as I said it killed
networking. The problem was in Norton Internet Securities 2003
Firewall/Home Networking settings. 192.168.10.0 was the only trusted
connection available and allowed during its installation. I removed this
and added 192.168.0.0 on both machines. Wha-la! The thing that chaps my
ass is in all the troubleshooting documents all over the web it recommended
you to check your firewall settings. I ignored this because heck, it worked
before? What could be wrong with it? Lessoned learned. Let's move on.

It may take a while to forget this one

Thanks!

Gary