Network slowage?

Hello, Group:

I was hoping somebody can shine some light on why this network is so
slow:

Old configuration that worked:

Subnet #1 192.168.2.0/24 - routing through with IPTables to another
machine
192.168.1.1, finally this machine arrives at the Internet.

Subnet #2 192.168.1.0/24 - routing through with IPTables to INET
router.

New configuration:

The new config takes 192.168.1.0/24, routes through 192.168.1.1, then
to 192.168.2.1 (running SBS2003 with RRAS NAT enables), and finally
192.168.2.1 connects to the Internet since this machine has two NICS
installed.

All the clients on 192.168.2.0/24 route fine through new Windows
machine running NAT with Dual Public/Private ip address, but now all
the clients on the 192.168.1.0/24 take apx. 1-2 minutes to start a
connection to the Internet, but once the clients bring up a web page,
the browsing is fine.

Regards,

--TJ

On Fri, 14 Apr 2006 16:29:38 -0700, techjohnny wrote:

> Hello, Group:
>
> I was hoping somebody can shine some light on why this network is so
> slow:
>
> Old configuration that worked:
>
> Subnet #1 192.168.2.0/24 - routing through with IPTables to another
> machine
> 192.168.1.1, finally this machine arrives at the Internet.
>
> Subnet #2 192.168.1.0/24 - routing through with IPTables to INET
> router.
>
> New configuration:
>
> The new config takes 192.168.1.0/24, routes through 192.168.1.1, then
> to 192.168.2.1 (running SBS2003 with RRAS NAT enables), and finally
> 192.168.2.1 connects to the Internet since this machine has two NICS
> installed.
>
> All the clients on 192.168.2.0/24 route fine through new Windows
> machine running NAT with Dual Public/Private ip address, but now all
> the clients on the 192.168.1.0/24 take apx. 1-2 minutes to start a
> connection to the Internet, but once the clients bring up a web page,
> the browsing is fine.
>
> Regards,
>
> --TJ

Hi, didn't read your lines abt subnetting and routing. Just noted the "1-2
minutes" you mentioned.

For my part - in nine cases of ten every starup delay in the order of 45
secs or multiples thereof are related to the DNS not working, or not being
reached. Or that some service needing it doesn't find it the usual way.
After a timeout (45 secs or so) things usually work ok.

Just my 5 cent...

/dex

--
http://www.artiesoft.com/gutenberg/search/

Finagle's fourth Law:
Once a job is fouled up, anything done to improve it only makes
it worse.

On Fri, 14 Apr 2006 16:29:38 -0700, techjohnny wrote:

> Hello, Group:
>
> I was hoping somebody can shine some light on why this network is so
> slow:
>
> Old configuration that worked:
>
> Subnet #1 192.168.2.0/24 - routing through with IPTables to another
> machine
> 192.168.1.1, finally this machine arrives at the Internet.
>
> Subnet #2 192.168.1.0/24 - routing through with IPTables to INET
> router.
>
> New configuration:
>
> The new config takes 192.168.1.0/24, routes through 192.168.1.1, then
> to 192.168.2.1 (running SBS2003 with RRAS NAT enables), and finally
> 192.168.2.1 connects to the Internet since this machine has two NICS
> installed.
>
> All the clients on 192.168.2.0/24 route fine through new Windows
> machine running NAT with Dual Public/Private ip address, but now all
> the clients on the 192.168.1.0/24 take apx. 1-2 minutes to start a
> connection to the Internet, but once the clients bring up a web page,
> the browsing is fine.
>
> Regards,
>
> --TJ

I've not seen anything approaching minutes, but I did troubleshoot a
situation last year where there was about a 45 second delay in address
resolution.

step 1 - disable IPV6 - this cut the 45 second delay to about 12 seconds
step 2 - insert 'option timeout:0' in the /etc/resolv.conf file - this
eliminates the 12 second time lag.

Yes, disabling IPv6, which is enabled by default on Fedora Core 2,
fixed my slow network access from Subnet #2.

Also, I found this documented on the Internet after doing a "Google
Search."

Thanks!