Arnie,
I'm sure you're right. . . but I also have an NT Proxy (P.S. II - on
the same box - I've been booting around the 20 gig NT belmouth and using
a 1.1 meg STN install from floppy!!) NT Proxy never gives this error.
(i.e. the browser always waits for the connection.)
Another thing I have noticed - lets say that the browser will wait 2.5
minutes before giving up. . . STN often takes less time than that to
get a good connection (say a minute to 1.5 min) Once it tries, it does
not work, even after the connection is made, until it fails the first
time and I re-try (via reload).
I could understand this in the case where the ISP stinks, and it takes
five min to get a connection. . . I would expect a time-out!
I suspect that the initial request that initiated the dial-out was not
being cached by STN, and ends up getting lost.
Jim
Arnie Rothenbaum wrote:
> Jim,
>
> I'm going to take a guess here.
>
> Your workstation running the browser always thinks it's connected to the
> net. The winsock is loaded and Netscape / IE sees this as connected.
>
> When you pass the URL request to STN it says "time to make the donuts"
> and
> dials out, but the browser thinks it is already passed the URL request
> out
> to the net .... and waits for a response. It doesn't ask a second time
> but
> just waits. If you were to click reload a couple times before the
> time-out
> STN would have reconnected and you're hit the site with no error.
>
> This is no different than if you had dialed in to the net directly (say
> through AOL, god forbid), minimized the AOL connection and ran Netscape
> or
> IE. Then AOL, while minimized said "Good-bye" and you lost the
> connection.
> Netscape and IE would just sit their and wait for the connection to that
> URL
> that you just clicked on. And wait, and wait, until it times out. Then
> you'd realize that AOL kicked you off. Redial AOL, get back in and
> retry
> Netscape / IE again and it is back on track.
>
> I have a client using STN in another room that dials out. They don't
> get to
> hear the phone dial, nor do they hear the consistent hang ups and
> redials
> (because the ISP sucks and connects one out of five times) so they get
> the
> time-out error a few times. Although they usually just call in for
> e-mail;
> I make them load Netscape Navigator first. When they see the home page
> load, it is ok to pick up the e-mail (as they are now online).
>
> Get cable or DSL and you'll never wait. You're on 24x7.
>
> Good Luck,
> Arnie
>
> Jim Harris wrote:
>
> > Here's one for the books. . .
> >
> > I have STN running. Dials out, works like a champ. I have an
> > inactivity time out setting of "x" minutes. After "x" minutes, the
> > modem hangs up. (as it is supposed to. . .)
> >
> > OK, say the modem is on-hook. I make a network request via my web
> > browser. The modem picks up, dials, and makes a connection. (again, as
> > it should.)
> >
> > Here's the beef: The -FIRST- time I try to use the browser to get a
> > page, if the modem is not already on line, it -always- fails, even after
> > picking up the line, dialing, and connecting. Once it is connected,
> > (and Netscape or IE tell me that it cannot find the page/server), if I
> > retry, it always succeeds. If the connection is already established, it
> > always succeeds.
> >
> > WHY does it fail at initial connect?
> >
> > WHAT can I do to make it work?
> >
> > Thanks!!
> >
> > Jim
> > --
> > Visit http://www.ShareTheNet.com for info about ShareTheNet
> > Visit http://www.topica.com/lists/sharethenet for info about this list
> > _________________________________________________________
> > Enlighten your in-box. http://www.topica.com/t/15
>
--
Visit http://www.ShareTheNet.com for info about ShareTheNet
Visit http://www.topica.com/lists/sharethenet for info about this list
_________________________________________________________
Enlighten your in-box. http://www.topica.com/t/15
