🚀 go-pugleaf

In <89sq3g$o8v$1@samba.rahul.net> "Jim Hurley"
<hurleyj@94.usenet.us.com> writes:

>Now it takes about 3 minutes to connect (before it took about 10-15 seconds).

In the recent discussion, the solution that worked was to uncheck the
'log on to network' checkbox.

>I have a static IP address of 204.95.65.92 = 0xcc5f415c and I
>configured the machine with a static IP address in the TCPIP
>properties.

>Note below that that wasn't accepted, maybe because that computer's
>name isn't 'krell' - the hostname I normally use....

This is supposed to work, regardless of host name.

>03-04-2000 12:46:28.31 - IPCP : IP address is cc5f415c.
>                                                               ---------- IP->204.95.65.92 => 'krell.arachnaut.org'
...
>03-04-2000 12:46:28.42 - IPCP : Received and accepted IP address of c0a00d10.
>                                                                                                ---------  IP->192.160.13.16

192.160.13.16 is the native IP address of the terminal server to whichof
the terminal server to which you are connecting.  Are you sure that the
last debugging entry above indicates the IP address assigned to you?  It
might be just the terminal server identifying itself.  Have you found
any documentation that describes what these log entries mean?  If not, I
would not put too much faith in them.  Specifically, those debugging
entries don't specify whose IP address is being shown.

Do you have the 'use default gateway' box checked?  If not, please check
it.  If it's not checked, your machine might try to route outgoing
traffic through the IP address of the terminal server.  That might not
work, because it's not on the same network as your machine is.
-- 
(Rahul Dhesi)
a2i network support account <support@rahul.net>