Netmasks incorrect in PM
Kendrick Myatt (myattk@cherokee.datatek.com)
Thu, 05 Sep 1996 10:40:10 -0500
A strange thing happened this morning... I had a couple of users who
connected with a netmask of 255.255.255.255, although their software (1
win95, 1 winsock) correctly specified the proper netmask. As a result, all
of their packets queued and were flushed, making them pretty much stuck in
the water.
I have not seen this behavior before, and the users had never run into a
problem before accessing anything, so this must be a first-time issue. What
could cause this, and how do I make it stop? When I had them hang up and
dial back in, the same thing happened again. Strange...
TIA for any ideas,
Kendrick