Help with Network Segregation

[RazorsEdge]

I'm playing around with a server 2003 installation that I would like to do DHCP and DNS for a couple of test workstations. I have a Verizon FIOS Actiontec router for my main home network, and to this I've attached an old Linksys BEFSR41 (with a crossover cable to the Linksys WAN port) to do the segregation. I followed the EZLAN guide, but can't get the two devices to see each other.

Here is my setup:
actiontec 192.168.1.1
Linksys 192.168.2.1 (LAN IP address in setup)
server 2003 box is 192.168.2.2, and can access the Linksys router without problem, but can't ping the Actiontec router

Also, from the actiontec status page, I can see that it has a device at 192.168.1.20 (the WAN IP address I gave the Linksys), but I can't ping the Linksys from the Actiontec setup menu.

Do I need to be configuring the default gateway address and DNS on the linksys? What should these be set to?

Hardware isn't the problem ( I don't think) and the crossover cable is brand new.

Any help would be appreciated

 

[Crusty]

Yes, the linksys needs a gateway otherwise it won't know where to send traffic that's not on it's network. It should be the IP of your actiontec router.

 

[RazorsEdge]

For the Linksys setup, it says that a DNS address is required. Should I point that to the actiontec as well, or because this network is segregated, should it be the DNS server (my server 2003 box)?

 

[Crusty]

It doesn't matter where your DNS server is located as long as you can get to it from the PC that needs it. In your case, it'll be just fine to set the DNS servers in the linksys to point to the IP of the actiontec. You can as many DNS servers on a network as you want, but you only need one

 

[drebo]

You should use a straight patch cable, not a crossover cable for this. You're connecting an autonomous device to a switch (even though that switch is in another autonomous device). This is likely the cause of your connection issues. Many devices are autosensing, but there are still a lot that aren't.

 

[Crusty]

Originally posted by: drebo
You should use a straight patch cable, not a crossover cable for this. You're connecting an autonomous device to a switch (even though that switch is in another autonomous device). This is likely the cause of your connection issues. Many devices are autosensing, but there are still a lot that aren't.

Bah, not sure how I glanced over that in the OP. Good point!

 

[RazorsEdge]

I'll try a regular cable tonight. Do I still connect the Linksys WAN port to the Actiontec router, or should I use a regular port or the uplink? Maybe the EZLAN site was wrong - this was the part I was following:

Disconnect the Computers that you would like to be protected from the Front Wireless Router and plug them into the second (Shield) Router. Connect the WAN port of the second Router (using a crossover cable) to one of the regular port of the Wireless Router.

 

[RazorsEdge]

Just tried it with a patch cable between the routers and it worked fine (regular port on Actiotec, WAN port on Linksys). Crossover was the problem. Thanks for the help!