As far as this problem goes, it's getting wierder by the minute. The user
says he can dial in and surf the web fine, but whenever he tries to
connect to a machine that is using TCP wrappers (his reason for needing a
static IP), the connection is refused returning the IP address of the
portmaster he's connected to as the IP that's being refused.
We've seen him logged in, and for about 50% of the time, we cannot ping
him from a machine on our network. During one connect, my parner reported
not being able to ping him until after pinging the portmaster he was
connected to first. By the time I got to try it, he was logged in again on
another portmaster. I was able to ping him at first, but then later was
not able to ping him, despite his still being connected. I logged into the
portmaster, and was still unable to ping him. I did, however, notice that
each time I pinged him, his idle time reset to 0.
I've dialed in as him, on all of our portmasters, and I've been able to
connect out just fine, as well as ping myself, etc.
I suspect it's a problem on his end, but he has been a long time user who
has only started experiencing this problem in the last week or so, after
we upgraded our portmasters to comos 2.7.2 from 3.3.1. Even if he did make
a change, I have no idea what change he could have made that would cause a
TCP wrapper to report a connection from the IP of a portmaster through
multiple connects, reporting the IP of the different portmasters he was
logged into each time.
-Jason
On Thu, 15 Jan 1998, Tom wrote:
>
> On Fri, 16 Jan 1998, Jason Hatch wrote:
>
> > You may be right. I haven't interviewed the user myself. I thought the
> > default gateway was usually assigned to "self" in Win95 (probably because
> > it's a broadcast node).
>
> "broadcast node"? I've been doing IP for a while now, but I don't
> understand that. Nothing is getting broadcast here.
>
> The gateway IP is set to the far end address. That is the way it is
> supposed to work.
>
> > -Jason
>
> Tom
>
> > On Thu, 15 Jan 1998, Tom wrote:
> >
> > >
> > > On Thu, 15 Jan 1998, Jason Hatch wrote:
> > >
> > > > We're having a strange problem. One of our users who has a static IP is
> > > > dialing in and (according to hist windows95 "winipcfg") he's getting
> > > > configured with the IP address of the PORTMASTER's ethernet interface. Has
> > > > anyone experienced this problem?
> > >
> > > If the address is in the "Default Gateway" box, it is normal, if it is
> > > in the "IP Address" field, there is a problem. I suspect that the user is
> > > confused.
> > >
> > > > -Jason
> > >
> > > Tom
> > >
> > > -
> > > To unsubscribe, email 'majordomo@livingston.com' with
> > > 'unsubscribe portmaster-users' in the body of the message.
> > >
> >
> >
> >
>
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.