Dan,
I think you'll find this is specifically a Win95 problem and it is at the
client end. It has nothing to do with the PM. It seems to happen most
often when more than one protocol (IPX and/or NetBEUI as well as TCP/IP)
is installed in "NETWORKS". For some reason Win95 can't seem to keep the
bindings straight and will periodically use another protocol (or NO
protocol) when trying to make the connection.
Seems to be fixed in the latest bug fix... er... there are no bugs in
Win95... it's the latest "enhancement" release!
Regards,
Steve
-----------------
that's not the case. we have this same thing. it is load dependent
and win3.1 and 95 both see it. not many 95'ers but almost every
3.1 using the shiva dialler. the login prompt definately responds
slower depending on portmaster load. call a loaded one with a terminal
program and watch it. in this state if a 95'r tries to allow the
portmaster to give it the dns it will sometimes crash 95 altogether.
i have 4 megs in all my portmasters, but that made notta.... we have
every 3.1 user with the shiva dialer bring up the 3rd party security
window to get in. they just hit continue [f7] and away they go. only
a few 95 users need this. on an empty portmaster nobody needs it.
looks like a lack of horsepower to me.
scott leonello
harbor communications
One of the lessons of history is that nothing is often a good thing to do
and always a clever thing to say. -- Will Durant