XP Local Workgroup: cannot see behind router?

[Guest]

Any help here, much appreciated.
I run via DSL, which connects via the Actiontec wierless gateway. This
gateway has a single rj45 to directly connect one PC, and others via wireless.

I need to connect more than 1 pc when the wireless has a snafu (as it had
this past week). I connected a Linksys Etherfast DSL router with 4 ports to
the actiontec, and then connect the PCs into the router. This router does
have its default DHCP serving turned off, as the Actiontec is doing this
function.

All PCs can see the internet and work that way; the actiontec lists all
devices as active and there in its active user list. All PC run MS XP Pro
SP2+(all recent patches as they arrive) and are defined to be part of my
named workgroup.

When my desk pc is connected to the actiontec directly via its single port,
XP can see the other PCs in the workgroup, and they can see it. All in one
MS XP network workgroup and working together as it should be.

When the desk pc is connected to a port of the linksys router, which is
connected to the single actiontec port, this desk pc XP network cannot see
the others in the group, and the others in the group cannot see the desk pc.

Again, the actiontec does show that all pc's names are recognized and
active, all part of the same internal LAN [192.168.0.x]; why would one set of
wireless connected systems be able to see each other in the MS work group and
not the one(s) recognized but behind the linksys router [though in the same
LAN]?

Is this an MS XP networking issue or some very-obscure gateway+router
configuration problem I've not yet addressed? All devices on the net are
tagged as part of my named workgroup- I'd expect MS should see them as such.

 

[John Wunderlich]

Any help here, much appreciated.
I run via DSL, which connects via the Actiontec wierless
gateway. This
gateway has a single rj45 to directly connect one PC, and others
via wireless.

I need to connect more than 1 pc when the wireless has a snafu (as
it had this past week). I connected a Linksys Etherfast DSL
router with 4 ports to the actiontec, and then connect the PCs
into the router. This router does have its default DHCP serving
turned off, as the Actiontec is doing this function.

All PCs can see the internet and work that way; the actiontec
lists all devices as active and there in its active user list.
All PC run MS XP Pro SP2+(all recent patches as they arrive) and
are defined to be part of my named workgroup.

When my desk pc is connected to the actiontec directly via its
single port, XP can see the other PCs in the workgroup, and they
can see it. All in one MS XP network workgroup and working
together as it should be.

When the desk pc is connected to a port of the linksys router,
which is connected to the single actiontec port, this desk pc XP
network cannot see the others in the group, and the others in the
group cannot see the desk pc.

Again, the actiontec does show that all pc's names are recognized
and active, all part of the same internal LAN [192.168.0.x]; why
would one set of wireless connected systems be able to see each
other in the MS work group and not the one(s) recognized but
behind the linksys router [though in the same LAN]?

Is this an MS XP networking issue or some very-obscure
gateway+router configuration problem I've not yet addressed? All
devices on the net are tagged as part of my named workgroup- I'd
expect MS should see them as such.

When you connect the Actiontec to the Linksys, did you use one of
the LAN ports on the Linksys? Attaching to the WAN port will cause
the router to act like a firewall. What you really need is a switch
rather than a router.

HTH,
john

 

[Guest]

The linksys also has an upstream-port that is supposed to let that work, but
it didn't. Guess a simple hub/ switch is what I need? The confusing part
was that all of them were working in a LAN that the lan-managing gateway saw
as the same, and all show the proper names.

Any help here, much appreciated.
I run via DSL, which connects via the Actiontec wierless
gateway. This
gateway has a single rj45 to directly connect one PC, and others
via wireless.

I need to connect more than 1 pc when the wireless has a snafu (as
it had this past week). I connected a Linksys Etherfast DSL
router with 4 ports to the actiontec, and then connect the PCs
into the router. This router does have its default DHCP serving
turned off, as the Actiontec is doing this function.

All PCs can see the internet and work that way; the actiontec
lists all devices as active and there in its active user list.
All PC run MS XP Pro SP2+(all recent patches as they arrive) and
are defined to be part of my named workgroup.

When my desk pc is connected to the actiontec directly via its
single port, XP can see the other PCs in the workgroup, and they
can see it. All in one MS XP network workgroup and working
together as it should be.

When the desk pc is connected to a port of the linksys router,
which is connected to the single actiontec port, this desk pc XP
network cannot see the others in the group, and the others in the
group cannot see the desk pc.

Again, the actiontec does show that all pc's names are recognized
and active, all part of the same internal LAN [192.168.0.x]; why
would one set of wireless connected systems be able to see each
other in the MS work group and not the one(s) recognized but
behind the linksys router [though in the same LAN]?

Is this an MS XP networking issue or some very-obscure
gateway+router configuration problem I've not yet addressed? All
devices on the net are tagged as part of my named workgroup- I'd
expect MS should see them as such.

When you connect the Actiontec to the Linksys, did you use one of
the LAN ports on the Linksys? Attaching to the WAN port will cause
the router to act like a firewall. What you really need is a switch
rather than a router.

HTH,
john

 

[Chuck]

Any help here, much appreciated.
I run via DSL, which connects via the Actiontec wierless
gateway. This
gateway has a single rj45 to directly connect one PC, and others
via wireless.

I need to connect more than 1 pc when the wireless has a snafu (as
it had this past week). I connected a Linksys Etherfast DSL
router with 4 ports to the actiontec, and then connect the PCs
into the router. This router does have its default DHCP serving
turned off, as the Actiontec is doing this function.

All PCs can see the internet and work that way; the actiontec
lists all devices as active and there in its active user list.
All PC run MS XP Pro SP2+(all recent patches as they arrive) and
are defined to be part of my named workgroup.

When my desk pc is connected to the actiontec directly via its
single port, XP can see the other PCs in the workgroup, and they
can see it. All in one MS XP network workgroup and working
together as it should be.

When the desk pc is connected to a port of the linksys router,
which is connected to the single actiontec port, this desk pc XP
network cannot see the others in the group, and the others in the
group cannot see the desk pc.

Again, the actiontec does show that all pc's names are recognized
and active, all part of the same internal LAN [192.168.0.x]; why
would one set of wireless connected systems be able to see each
other in the MS work group and not the one(s) recognized but
behind the linksys router [though in the same LAN]?

Is this an MS XP networking issue or some very-obscure
gateway+router configuration problem I've not yet addressed? All
devices on the net are tagged as part of my named workgroup- I'd
expect MS should see them as such.

When you connect the Actiontec to the Linksys, did you use one of
the LAN ports on the Linksys? Attaching to the WAN port will cause
the router to act like a firewall. What you really need is a switch
rather than a router.

HTH,
john

The linksys also has an upstream-port that is supposed to let that work, but
it didn't. Guess a simple hub/ switch is what I need? The confusing part
was that all of them were working in a LAN that the lan-managing gateway saw
as the same, and all show the proper names.

Bernie,

There are actually 3 key steps to this procedure.
1) Connect the 2 routers LAN - LAN.
2) Disable the DHCP server on the second router!
3) Restart, or renew IP settings on, each computer connected to router #2. Each
computer connected to router #2 has to get new IP settings. If they have the
old settings, they will still be on their own subnet, and the computers
connected to router #1 won't see them.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-on-lan-with-two-routers.html>
http://nitecruzr.blogspot.com/2005/06/file-sharing-on-lan-with-two-routers.html

If you still have a problem, look at "browstat status" and "ipconfig /all" from
each computer, and diagnose the problem. Read this article, and linked
articles, and follow instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

 

[Richard G. Harper]

You need to disable the router functions on the Etherfast DSL router when
connecting it to the Actiontec in this manner, or dump the Etherfast DSL
router entirely and use a simple network hub or switch instead.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

thanks Chuck- will do.

Any help here, much appreciated.
I run via DSL, which connects via the Actiontec wierless
gateway. This
gateway has a single rj45 to directly connect one PC, and others
via wireless.

I need to connect more than 1 pc when the wireless has a snafu (as
it had this past week). I connected a Linksys Etherfast DSL
router with 4 ports to the actiontec, and then connect the PCs
into the router. This router does have its default DHCP serving
turned off, as the Actiontec is doing this function.

All PCs can see the internet and work that way; the actiontec
lists all devices as active and there in its active user list.
All PC run MS XP Pro SP2+(all recent patches as they arrive) and
are defined to be part of my named workgroup.

When my desk pc is connected to the actiontec directly via its
single port, XP can see the other PCs in the workgroup, and they
can see it. All in one MS XP network workgroup and working
together as it should be.

When the desk pc is connected to a port of the linksys router,
which is connected to the single actiontec port, this desk pc XP
network cannot see the others in the group, and the others in the
group cannot see the desk pc.

Again, the actiontec does show that all pc's names are recognized
and active, all part of the same internal LAN [192.168.0.x]; why
would one set of wireless connected systems be able to see each
other in the MS work group and not the one(s) recognized but
behind the linksys router [though in the same LAN]?

Is this an MS XP networking issue or some very-obscure
gateway+router configuration problem I've not yet addressed? All
devices on the net are tagged as part of my named workgroup- I'd
expect MS should see them as such.


When you connect the Actiontec to the Linksys, did you use one of
the LAN ports on the Linksys? Attaching to the WAN port will cause
the router to act like a firewall. What you really need is a switch
rather than a router.

HTH,
john

The linksys also has an upstream-port that is supposed to let that work, but
it didn't. Guess a simple hub/ switch is what I need? The confusing part
was that all of them were working in a LAN that the lan-managing gateway saw
as the same, and all show the proper names.

Bernie,

There are actually 3 key steps to this procedure.
1) Connect the 2 routers LAN - LAN.
2) Disable the DHCP server on the second router!
3) Restart, or renew IP settings on, each computer connected to router #2. Each
computer connected to router #2 has to get new IP settings. If they have the
old settings, they will still be on their own subnet, and the computers
connected to router #1 won't see them.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-on-lan-with-two-routers.html>
http://nitecruzr.blogspot.com/2005/06/file-sharing-on-lan-with-two-routers.html

If you still have a problem, look at "browstat status" and "ipconfig /all" from
each computer, and diagnose the problem. Read this article, and linked
articles, and follow instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp