I have a wireless router with IP address 192.168.2.1 with DHCP enabled. I have a wireless desktop client that was allocated 192.168.2.3 It is set for internet sharing and it's ICS provides 192.168.0.x addresses. These are all XP Pro systems.
They all can connect just fine to the internet, but I cannot access SomeWiredClient directly from MyWiredLaptop. I can use VNC (or remote desktop) to connect to MyWirelessServer and then from that desktop, connect to SomeWiredClient.
This should have worked:
route add 192.168.0.0 mask 255.255.255.0 192.168.2.3
All it did was to prevent my laptop from accessing the AT&T Seimens modem.
I suspect the problem is that the ATT device is 192.168.0.1 and that conflicts with the same IP address that the wireless desktop server is using for its DHCP clients.
If I cant get this to work then I will have to buy one of those wireless print servers that allow computers to connect in addtion to printers.
I am not sure how you connect to them, but use tracert command may help.
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Joseph Stateson" <josephstateson@att.net> wrote in message news:agD0k.7047$nW2.2500@nlpi064.nbdc.sbc.com...
I have a wireless router with IP address 192.168.2.1 with DHCP enabled. I have a wireless desktop client that was allocated 192.168.2.3 It is set for internet sharing and it's ICS provides 192.168.0.x addresses. These are all XP Pro systems.
They all can connect just fine to the internet, but I cannot access SomeWiredClient directly from MyWiredLaptop. I can use VNC (or remote desktop) to connect to MyWirelessServer and then from that desktop, connect to SomeWiredClient.
This should have worked:
route add 192.168.0.0 mask 255.255.255.0 192.168.2.3
All it did was to prevent my laptop from accessing the AT&T Seimens modem.
I suspect the problem is that the ATT device is 192.168.0.1 and that conflicts with the same IP address that the wireless desktop server is using for its DHCP clients.
If I cant get this to work then I will have to buy one of those wireless print servers that allow computers to connect in addtion to printers.
On Sun, 1 Jun 2008 15:03:06 -0500, "Joseph Stateson"
<josephstateson@att.net> wrote:
>I have a wireless router with IP address 192.168.2.1 with DHCP enabled. I have a wireless desktop client that was allocated 192.168.2.3 It is set for internet sharing and it's ICS provides 192.168.0.x addresses. These are all XP Pro systems.
>
>AT&T DSL gateway (assigned 192.168.0.1 and I cant change it)
> USR-Wireless 192.168.2.1
> MyWiredLaptop 192.168.2.2
> MyWirelessServer 192.168.2.3 interface1=USB wireless
> MyWirelessServer 192.168.0.1 interface2=100BaseT
> SomeWiredClient 192.168.0.138
>
>They all can connect just fine to the internet, but I cannot access SomeWiredClient directly from MyWiredLaptop. I can use VNC (or remote desktop) to connect to MyWirelessServer and then from that desktop, connect to SomeWiredClient.
>
>This should have worked:
>route add 192.168.0.0 mask 255.255.255.0 192.168.2.3
>
>All it did was to prevent my laptop from accessing the AT&T Seimens modem.
>
>I suspect the problem is that the ATT device is 192.168.0.1 and that conflicts with the same IP address that the wireless desktop server is using for its DHCP clients.
>
>If I cant get this to work then I will have to buy one of those wireless print servers that allow computers to connect in addtion to printers.
>
>..thanks..
On MyWirelessServer, disable ICS, then create a network bridge between
the wireless and 100BaseT connections. That will combine the wireless
and wired networks into a single 192.168.2.x subnet. I've written a
web page with details:
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.
Thanks Steve - I looked at your site and followed the guide but was unable
to make it work. I went back to useing microsoft's zero wireless instead of
the dlink tool thinking that the dlink one was not working with the bridge.
It didnt make any difference and did not work anyways.
This is the best I could do:: http://tinyurl.com/6yg8en
Disconnecting the dlink usb wireless from the bridge immediately restored
the internet access and the ping to 192.168.2.3 work. Adding the wireless
to the bridge immediately caused the ping to fail. You can see that it is
failing when the USB wireless is added to the bridge (from that picture url)
Question:: How does the OS know that the wireless is where the internet is
and not the local connection? Could the data flow be reversed on the
bridge?
Also, I have more problems than just getting the bridge to work. The USB
device does not seem to allow a service install so I have to have autologin
enabled before the USB device is enabled. All these systems are running
BOINC and I want to be able to control them from a laptop but I can put the
control program on the wireless server which gives me access to all
computer, wired or wireless. That system must have autologin or the USB
wont work.
(sorry I emailed it, got hone and reposted original)
"Robert L. (MS-MVP)" <findemail@chicagotech.net> wrote in message news:OzpSbkFxIHA.5832@TK2MSFTNGP02.phx.gbl...
I am not sure how you connect to them, but use tracert command may help.
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Joseph Stateson" <josephstateson@att.net> wrote in message news:agD0k.7047$nW2.2500@nlpi064.nbdc.sbc.com...
I have a wireless router with IP address 192.168.2.1 with DHCP enabled. I have a wireless desktop client that was allocated 192.168.2.3 It is set for internet sharing and it's ICS provides 192.168.0.x addresses. These are all XP Pro systems.
They all can connect just fine to the internet, but I cannot access SomeWiredClient directly from MyWiredLaptop. I can use VNC (or remote desktop) to connect to MyWirelessServer and then from that desktop, connect to SomeWiredClient.
This should have worked:
route add 192.168.0.0 mask 255.255.255.0 192.168.2.3
All it did was to prevent my laptop from accessing the AT&T Seimens modem.
I suspect the problem is that the ATT device is 192.168.0.1 and that conflicts with the same IP address that the wireless desktop server is using for its DHCP clients.
If I cant get this to work then I will have to buy one of those wireless print servers that allow computers to connect in addtion to printers.
net help on route add 
Linear Mode
