We're an ISP using Livingston PM2's and PM3's. The PM2's are connected to
Microcom FAST RACK and Microcom ISPorte modems. We're using BSD/OS v3.0
running radius 1.16. (Was using 2.0 but 1.16 was distributed with BSD 3.0)
as our authentication server. Here's the deal:
NT 4.0 Workstation users can connect to us just fine. Once they're online
we can ping them, they can ping us, and they can ping anyone else on the
Internet. But, when they open, say Internet Explorer, or any Internet app,
all they get is host contacted waiting for reply, end of story. DNS is
resolving correctly with nslookup, etc... I've talked to the techs at
Microsoft who tell me that there's no difference between the way Win95 and
NT 4.0 do their dial-in connections (BS), and they had no idea why this was
happening.
When I put the Portmaster into debug 0x51 mode, I noticed that every time I
attempted to access a particular site with NT 4.0, the PM would return the
message 'Bad Expected xxxxx got 301' where xxxxx was an int and changed
every time. Needless to say this didn't give me much info as to what was
going on (refer to paragraph 1)
I stumbled on to the solution today though, finally. At first I thought
the NT 4.0 users needed a static IP Address, which actually seemed to fix
the problem. Actually, all they need is their username listed in the
/etc/raddb/users file. Once that username is listed in the users file, the
connection works great, every time, with dynamic addressing. Once that
entry is taken out of the users file, the connection works as described
above. Anyone have any idea why this is???