2 gateways causing problems

[benzguy777]

I recently had one gateway on my 30 user network connected through a linksys befsr41 and gateway of clients (XP Pro) set to the linksys IP which is 192.168.0.1.

The clients have the IP address of the server in the DNS and the Win2K Server's DNS forwarding is set to forward to the ISPs DNS.

Every was working well until I got another DSL line connected to the same ISP. Hooked this up to another Linksys BEFSR41 and gave it 192.168.0.2 IP. I now separated 5 computers and put the 192.168.0.2 IP on these 5 computers Gateway. Did this to separate the workload of different Internet tasks.

Now all these 5 PCs using the 192.168.0.2 gateway are having problems checking and sending mail. It takes these PCs so much longer to authenticate to my incoming and outgoing mail server hosted with another company - that I often get a timeout issue.

When I change the gateway of these 5 PCs back to 192.168.0.1 it authenticates so much faster.

What could be wrong?

 

[crazynoodle]

Did you change the subnet mask or does it remain the 255.255.255.0 (natural mask) ?

from a cmd prompt on the pc's pointing to 192.168.0.2 - do a tracert to the mail server and check out the path - does this look like what you expect?

 

[benzguy777]

The subnet of the 0.1 gateway is 255.255.255.0 for Interal/LAN. The Subnet of the problematic 0.2 gateway is also 255.255.255.0 for Internal/LAN and 255.255.255.248 for WAN/External.

These settings are from the Linksys Router.

I did a trace route and found that there was an extra HOP that always had "timeout" on the 0.2 gateway. I get 14 hops with no problems using the 0.1 and 15 hops with "always" a timeout using the 0.2 gateway.

Is this an issue with my DSL provider or aRouter setting issue?


Thanks!

 

[yizhar]

HI.

You should contact your ISP.

The problem in your case is not the usage of 2 different routers, but something related to the new connection itself.

Take a look here:

http://www.cisco.com/warp/public/110/21.html

Yes, I know that you don't have a pix but the problem could be related to a missing reverse lookup DNS PTR record.

Browse here from a workstation connected to 192.168.0.2:

http://www.showmyip.com

Use these to check reverse lookup of your IP address:

http://www.samspade.org/t/dns

http://www.dnsstuff.com

Yizhar Hurwitz

http://teachers.sivan.co.il/yizhar

 

[justcurious]

Your description of the problem sounds like it may be caused by your router configuration. Check the MTU setting at the bottom of the Filters page.

By default, MTU is disabled. You should enable it and set the value to 1492, which is the default value if memory serves me correctly.

To be sure, compare it with the value set on the existing router.

If this doesn't solve the problem, swap the routers. This won't fix the problem, but it will confirm or eliminate the router as the cause.

If you determine that the router is the cause and the MTU setting doesn't solve the problem, compare every setting on every page in the Linksys configurations. Then ask for help in the Linksys forum.