>Demetris Papallis wrote:
>>
>> > That bit of info is a Great HELP! Are you using Radius for authentication? If
>> > so make sure you have his authentication record setup properly - in other words,
>> > make sure the Radius record reflects PPP operation with PAP authetication ( damn,
>> > wish I was at the ISP site so I could get you a configuration record for an example!
>> > ).
>>
>> Yes, I'm using Radius for authentication and at least up to now I never had a problem
>> with authentication. This particular users' entry is as follows:
>>
>> user Password = "passwd", Simultaneous-Use = 1
>> Service-Type = Framed,
>> Framed-Protocol = PPP,
>> Framed-IP-Netmask = 255.255.255.255,
>> Framed-Routing = None,
>> Filter-Id = "std.user",
>> Framed-MTU = 1500
>>
>> Works for everybody else!
>>
>> > One other thought comes to mind ... What is the version of the software in the
>> > Portmaster? We had a problem with our Portmaster and Windows-95 until we upgraded
>> > to the latest revision!
>>
>> 3.3.2c1 is the name :) The latest one...
>>
>
>Well ... Let's see ... hummm... Let's review what we know...
>
>1. You have a user utilizing WIN-95 who can not negotiate a connection via PPP.
>
>2. Your RADIUS record for the user looks to be correct.
>
>3. You have the latest version of the PortMaster software installed.
>
>4. The WIN-95 user is the only one having this problem - all of your other WIN-95
> users connect properly.
>
>5. The WIN-95 user's system is responding to the Portmaster:
Win95 is *not* responsing. This sending LCP_CONFIGURE_REQUEST is from
the PM to Win95, not vice versa.
>
> >Sending LCP_CONFIGURE_REQUEST to port S6 of 20 bytes containing:
> >01 13 00 14 02 06 00 00 00 00 05 06 7c 02 d5 2c
> >07 02 08 02
>
> Which translates to: (supplied by Michael J. Hartwick - thanks)
>
> LCP-Configure-Request
> ID = 13
> Length = 14
> Async-Control-Character-Map = 00000000
> Magic-NUmber = 7c02d52c
> Protocol-Field-Compression
> Address-and-Control-Field-Compression
>
> >Sending LCP_CONFIGURE_REQUEST to port S6 of 20 bytes containing:
> >01 14 00 14 02 06 00 00 00 00 05 06 7c 02 d5 2c
> >07 02 08 02
>
> LCP-Configure-Request
> ID = 14
> Length = 14
> Async-Control-Character-Map = 00000000
> Magic-NUmber = 7c02d52c
> Protocol-Field-Compression
> Address-and-Control-Field-Compression
>
>6. Your user has only TCP/IP setup for the dialup connection without other
> protocols active.
>
>
>There does not seem to be very much left that could cause this problem. Some other
>possibilities:
>
>A. Is the WIN-95 user connected to a network (ethernet) and if so is the ethernet
> protocol set as the default (obscure BUT causes all sorts of problems)?
>
>B. If item A is false - does the user have WINS active?
>
>C. Does the user have the "dialin adapter" installed in the networking section?
>
>D. Is the current WIN-95 configuration a "left-over" from some other ISP
> configuration (possible conflict).
>
>I have seen this very issue arise sometimes and usually "walking" the user through a
>setup via telephone conversation fixes the problem. With all of the options in WIN-95
>for different protocols some obscure setting is not set correctly or there are
>multiple TCP/IP protocols defined in the "network" section [in the control panel
>section] which are not configured properly for dialup networking BUT are set as the
>default protocol.
>
>Good Luck ... Hope the info helps... GM
>
----------------------------------------------------------------------------
Michael J. Hartwick, VE3SLQ
Hartwick Communications Consulting
hartwick@primeline.net