I have a RH7.3 box setup as a server. My question is how long should it take to recognize a client (win 98) as established? When I open MSIE it dials in, connects then times out requiring a refresh to get going. I was wondering if this delay could be due to shorewall/iptables? /var/log/messages have nothing to indicate a problem with anything. My settings are mostly default except a few for ssh on the local network. Kev -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 1724 bytes Desc: not available Url : http://lists.shorewall.net/pipermail/shorewall-users/attachments/20030219/6202e920/winmail-0001.bin
Hi Kev At 09:17 19/02/03 -0500, Kevin Smith wrote:>I have a RH7.3 box setup as a server. My question is how long should it take >to recognize a client (win 98) as established? When I open MSIE it dials in, >connects then times out requiring a refresh to get going. I was wondering if >this delay could be due to shorewall/iptables?Do you mean that your Red Hat box is acting as an internet gateway, with a dial-up internet connection to the internet, and is connected to your Win 98 box by ethernet? Before I got broadband I was using a Linux box in this way (but without Shorewall or iptables) and often when first connecting the browser would report that a request had timed out simply because it can take ages to dial up. So my guess is that the problem is due to how long the dial-up process takes, and nothing to do with the setup of Shorewall or whatever. You could test this by getting the Red Hat box to dial up before starting to try to connect with the Win98 box. If you still get the delay/timeout then there might be a problem you need to investigate further. If not, then the dial-up delay is the likely culprit. cheers Julian -- jc@ljchurch.co.uk www.ljchurch.co.uk
Kevin I have setup 3 boxes that have Dial on Demand (I am assuming you are running the same) and this happens on all the networks, especially the two using analog dial ups. The one with an ISDN doesn''t due to the exceptionally quick logon to the internet. I came to the conclusion that the time it takes an analog connection to be established is "too" slow on and a timeout occurs. What I have done to make it seem better is to create a batch file that does an external ping and then fires up IE, and created a shortcut on the users desktop. Not elegant but works. If there is a better way I would not mind knowing of it. ;) Kim> -----Original Message----- > From: shorewall-users-bounces@lists.shorewall.net > [mailto:shorewall-users-bounces@lists.shorewall.net] > Sent: Wednesday, February 19, 2003 04:18 > To: Shorewall-Users > Subject: [Shorewall-users] Delayed browsing > > > I have a RH7.3 box setup as a server. My question is how long should it > take to recognize a client (win 98) as established? When I open MSIE it > dials in, connects then times out requiring a refresh to get going. I was > wondering if this delay could be due to shorewall/iptables? > /var/log/messages have nothing to indicate a problem with anything. My > settings are mostly default except a few for ssh on the local network. > > Kev << File: ATT00291.txt >>-------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 2856 bytes Desc: not available Url : http://lists.shorewall.net/pipermail/shorewall-users/attachments/20030219/a2347367/winmail.bin
Since you both suggested the same thing, Ill respond together. A> Yes it is a Gateway with the Win9x connected via eth0. Sorry, forgot to mention that. I thought that might be the issue, but on my other setup (win 98 workstation acting as a gateway) it dials in and come up soon as its connected. I have set both modems'' s11 register to 55 <fast dialing> that''s why I thought it my be the firewall slowly establishing the client<-> net connection. And Kim, that sounds like a workable solution. Thanks for you responses. Subject: Re: [Shorewall-users] Delayed browsing To: "Shorewall-Users" <shorewall-users@lists.shorewall.net> Message-ID: <5.1.1.6.0.20030219144420.023bd128@192.168.200.1> Content-Type: text/plain; charset="us-ascii"; format=flowed Hi Kev At 09:17 19/02/03 -0500, Kevin Smith wrote:>I have a RH7.3 box setup as a server. My question is how long should ittake>to recognize a client (win 98) as established? When I open MSIE it dialsin,>connects then times out requiring a refresh to get going. I was wonderingif>this delay could be due to shorewall/iptables?Do you mean that your Red Hat box is acting as an internet gateway, with a dial-up internet connection to the internet, and is connected to your Win 98 box by ethernet? Before I got broadband I was using a Linux box in this way (but without Shorewall or iptables) and often when first connecting the browser would report that a request had timed out simply because it can take ages to dial up. So my guess is that the problem is due to how long the dial-up process takes, and nothing to do with the setup of Shorewall or whatever. You could test this by getting the Red Hat box to dial up before starting to try to connect with the Win98 box. If you still get the delay/timeout then there might be a problem you need to investigate further. If not, then the dial-up delay is the likely culprit. cheers Julian -- jc@ljchurch.co.uk www.ljchurch.co.uk ------------------------------ Message: 3 Date: Wed, 19 Feb 2003 16:49:50 +0200 From: "Kim White" <kimw@megchem.co.za> Subject: RE: [Shorewall-users] Delayed browsing To: "Shorewall-Users" <shorewall-users@lists.shorewall.net> Message-ID: <NHBBKGJMMEEPHLKBICHHIENDDAAA.kimw@megchem.co.za> Content-Type: text/plain; charset="iso-8859-1" Kevin I have setup 3 boxes that have Dial on Demand (I am assuming you are running the same) and this happens on all the networks, especially the two using analog dial ups. The one with an ISDN doesn''t due to the exceptionally quick logon to the internet. I came to the conclusion that the time it takes an analog connection to be established is "too" slow on and a timeout occurs. What I have done to make it seem better is to create a batch file that does an external ping and then fires up IE, and created a shortcut on the users desktop. Not elegant but works. If there is a better way I would not mind knowing of it. ;) Kim