ICS Wizard fails to complete

[Guest]

Here's the job: to establish a shared connection using an XP-Pro box with a
wireless internet connection (host) for XP-Pro clients on a wired network.
Here's the problem: When Mr. Wizard runs, it goes out on the following
error: "Cannot complete the network setup wizard".

During the attempt, Firewall can be observed being disabled momentarily. At
the end of the failed setup, the LAN card initially has no address assigned,
then comes up with an Auto Private Address of 169.254.86.144 (sub:
255.255.0.0). There is no corresponding entry in the application, system or
security log.

Attempting a manual configuration has the same end result - no sharing.
Assigning 192.168.0.1 [sub: 255.255.255.0] to the LAN card on the Host and
assigning (or allowing DHCP to assign) the wireless nic 192.168.0.4 [sub:
255.255.255.0, gw: 192.168.0.100] from "Network Connections" comes the error
"...A LAN connection is already configured with the IP address required for
auto IP addressing."

Environment: The Host and single client run XP with all of the current
updates (to include TCP/IP v.6), communicate ok on the LAN, and the Host has
good internet connectivity. The wireless link on the Host is a Netgear
dual-band WAG311 that connects with a Netgear FWAG114, IP: 192.168.0.100
[sub:255.255.255.0] access point/firewall with DHCP enabled for the LAN and
connects to the WAN side via an ADSL modem. The host and client boxes are on
an ethernet cable with a Netgear FS105 auto-sensing, unmanaged, 5-port switch
in between.

I have experimented with all permutations of manual and auto configurations;
DHCP assignments on and off; Firewall enabled/disabled; Symantec A/V Corp.
Edition enabled/disabled; Microsoft Anti-Spyware disabled then removed;
client attached/removed....

What have I missed? Or, should I just go buy a Cisco wireless setup all
around and call it a day.

 

[Steve Winograd [MVP]]

Here's the job: to establish a shared connection using an XP-Pro box with a
wireless internet connection (host) for XP-Pro clients on a wired network.
Here's the problem: When Mr. Wizard runs, it goes out on the following
error: "Cannot complete the network setup wizard".

During the attempt, Firewall can be observed being disabled momentarily. At
the end of the failed setup, the LAN card initially has no address assigned,
then comes up with an Auto Private Address of 169.254.86.144 (sub:
255.255.0.0). There is no corresponding entry in the application, system or
security log.

Attempting a manual configuration has the same end result - no sharing.
Assigning 192.168.0.1 [sub: 255.255.255.0] to the LAN card on the Host and
assigning (or allowing DHCP to assign) the wireless nic 192.168.0.4 [sub:
255.255.255.0, gw: 192.168.0.100] from "Network Connections" comes the error
"...A LAN connection is already configured with the IP address required for
auto IP addressing."

Environment: The Host and single client run XP with all of the current
updates (to include TCP/IP v.6), communicate ok on the LAN, and the Host has
good internet connectivity. The wireless link on the Host is a Netgear
dual-band WAG311 that connects with a Netgear FWAG114, IP: 192.168.0.100
[sub:255.255.255.0] access point/firewall with DHCP enabled for the LAN and
connects to the WAN side via an ADSL modem. The host and client boxes are on
an ethernet cable with a Netgear FS105 auto-sensing, unmanaged, 5-port switch
in between.

I have experimented with all permutations of manual and auto configurations;
DHCP assignments on and off; Firewall enabled/disabled; Symantec A/V Corp.
Edition enabled/disabled; Microsoft Anti-Spyware disabled then removed;
client attached/removed....

What have I missed? Or, should I just go buy a Cisco wireless setup all
around and call it a day.

The wireless network uses the same 192.168.0.x/255.255.255.0 subnet
that ICS wants to assign to the local area network. To use ICS,
change the subnet for the wireless network something like 192.168.1.x.
That should be easy to do in the Netgear router's web-based setup
program.

If you enable ICS manually, instead of using the Wizard, don't assign
an IP address yourself. Let ICS do it.

Here's an alternative to ICS: create a network bridge on the "host"
computer, which will combine its wired and wireless networks into a
single network. Then, all of the computers can use the existing
192.168.0.x subnet.

The best solution might be to get an inexpensive USB wireless adapter
for the "client" computer so that it can connect directly to the
wireless network.
--
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

 

[Guest]

BRILLIANT!

I believe that I began an attempt to config a different subnet as described
(honest!) but my notes seem to trail off after a couple of days of on-and-off
experimentation. Nonetheless, I obviously did not complete a proper subnet
configuration.

The ADSL connection wants to be DHCP-boss for the WAN-side and creates
192.168.1.x for it's client. So, creating a subnet for the LAN-side of the
router (192.168.2.x) allows that DHCP server to be boss for incoming wireless
and wired conections.

Then, all this allows unencumbered, free reign to the shared internet
connection to get it's IP address automatically, and configure the final LAN
segment (back to 192.168.0.1) to be boss of DHCP to the remaining clients.
[Visio diagram available on request.]

This has made all things right in my little corner of the universe - it
really, really WORKS!

I can always count on these forums to get me back on the right track.
A thousand Thank Yous, Steve!
Regards,
-confusio

Here's the job: to establish a shared connection using an XP-Pro box with a
wireless internet connection (host) for XP-Pro clients on a wired network.
Here's the problem: When Mr. Wizard runs, it goes out on the following
error: "Cannot complete the network setup wizard".

During the attempt, Firewall can be observed being disabled momentarily. At
the end of the failed setup, the LAN card initially has no address assigned,
then comes up with an Auto Private Address of 169.254.86.144 (sub:
255.255.0.0). There is no corresponding entry in the application, system or
security log.

Attempting a manual configuration has the same end result - no sharing.
Assigning 192.168.0.1 [sub: 255.255.255.0] to the LAN card on the Host and
assigning (or allowing DHCP to assign) the wireless nic 192.168.0.4 [sub:
255.255.255.0, gw: 192.168.0.100] from "Network Connections" comes the error
"...A LAN connection is already configured with the IP address required for
auto IP addressing."

Environment: The Host and single client run XP with all of the current
updates (to include TCP/IP v.6), communicate ok on the LAN, and the Host has
good internet connectivity. The wireless link on the Host is a Netgear
dual-band WAG311 that connects with a Netgear FWAG114, IP: 192.168.0.100
[sub:255.255.255.0] access point/firewall with DHCP enabled for the LAN and
connects to the WAN side via an ADSL modem. The host and client boxes are on
an ethernet cable with a Netgear FS105 auto-sensing, unmanaged, 5-port switch
in between.

I have experimented with all permutations of manual and auto configurations;
DHCP assignments on and off; Firewall enabled/disabled; Symantec A/V Corp.
Edition enabled/disabled; Microsoft Anti-Spyware disabled then removed;
client attached/removed....

What have I missed? Or, should I just go buy a Cisco wireless setup all
around and call it a day.

The wireless network uses the same 192.168.0.x/255.255.255.0 subnet
that ICS wants to assign to the local area network. To use ICS,
change the subnet for the wireless network something like 192.168.1.x.
That should be easy to do in the Netgear router's web-based setup
program.

If you enable ICS manually, instead of using the Wizard, don't assign
an IP address yourself. Let ICS do it.

Here's an alternative to ICS: create a network bridge on the "host"
computer, which will combine its wired and wireless networks into a
single network. Then, all of the computers can use the existing
192.168.0.x subnet.

The best solution might be to get an inexpensive USB wireless adapter
for the "client" computer so that it can connect directly to the
wireless network.
--
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

 

[Steve Winograd [MVP]]

Here's the job: to establish a shared connection using an XP-Pro box with a
wireless internet connection (host) for XP-Pro clients on a wired network.
Here's the problem: When Mr. Wizard runs, it goes out on the following
error: "Cannot complete the network setup wizard".

During the attempt, Firewall can be observed being disabled momentarily. At
the end of the failed setup, the LAN card initially has no address assigned,
then comes up with an Auto Private Address of 169.254.86.144 (sub:
255.255.0.0). There is no corresponding entry in the application, system or
security log.

Attempting a manual configuration has the same end result - no sharing.
Assigning 192.168.0.1 [sub: 255.255.255.0] to the LAN card on the Host and
assigning (or allowing DHCP to assign) the wireless nic 192.168.0.4 [sub:
255.255.255.0, gw: 192.168.0.100] from "Network Connections" comes the error
"...A LAN connection is already configured with the IP address required for
auto IP addressing."

Environment: The Host and single client run XP with all of the current
updates (to include TCP/IP v.6), communicate ok on the LAN, and the Host has
good internet connectivity. The wireless link on the Host is a Netgear
dual-band WAG311 that connects with a Netgear FWAG114, IP: 192.168.0.100
[sub:255.255.255.0] access point/firewall with DHCP enabled for the LAN and
connects to the WAN side via an ADSL modem. The host and client boxes are on
an ethernet cable with a Netgear FS105 auto-sensing, unmanaged, 5-port switch
in between.

I have experimented with all permutations of manual and auto configurations;
DHCP assignments on and off; Firewall enabled/disabled; Symantec A/V Corp.
Edition enabled/disabled; Microsoft Anti-Spyware disabled then removed;
client attached/removed....

The wireless network uses the same 192.168.0.x/255.255.255.0 subnet
that ICS wants to assign to the local area network. To use ICS,
change the subnet for the wireless network something like 192.168.1.x.
That should be easy to do in the Netgear router's web-based setup
program.

If you enable ICS manually, instead of using the Wizard, don't assign
an IP address yourself. Let ICS do it.

Here's an alternative to ICS: create a network bridge on the "host"
computer, which will combine its wired and wireless networks into a
single network. Then, all of the computers can use the existing
192.168.0.x subnet.

The best solution might be to get an inexpensive USB wireless adapter
for the "client" computer so that it can connect directly to the
wireless network.

BRILLIANT!

I believe that I began an attempt to config a different subnet as described
(honest!) but my notes seem to trail off after a couple of days of on-and-off
experimentation. Nonetheless, I obviously did not complete a proper subnet
configuration.

The ADSL connection wants to be DHCP-boss for the WAN-side and creates
192.168.1.x for it's client. So, creating a subnet for the LAN-side of the
router (192.168.2.x) allows that DHCP server to be boss for incoming wireless
and wired conections.

Then, all this allows unencumbered, free reign to the shared internet
connection to get it's IP address automatically, and configure the final LAN
segment (back to 192.168.0.1) to be boss of DHCP to the remaining clients.
[Visio diagram available on request.]

This has made all things right in my little corner of the universe - it
really, really WORKS!

I can always count on these forums to get me back on the right track.
A thousand Thank Yous, Steve!
Regards,
-confusio

You're welcome, Confusio. I'm glad that my suggestion helped you
solve the problem.
--
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