[VOPRadius] New Update Available : Update 7 for VOP Radius 4.0 228

[Sysop]

Thanks Larry,       I got those from the on call guy last night about 3 am.  He originally started to give me one other and then said oh wait no we don't use that one anymore...maybe the extra one in your list.  You may want to ask them if you need the 27 as well...They have changed them on me in the past without so much as an email notification.   Pete   ----- Original Message ----- From: Larry Essary To: [EMAIL PROTECTED] Sent: Saturday, September 11, 2004 2:57 PM Subject: [VOPRadius] New Update Available : Update 7 for VOP Radius 4.0 228 At 02:18 PM 9/11/2004, you wrote: The radius server you have listed below is not one we show for DialUpUSA This is what we use so try the following 216.127.146.28 216.127.146.29 216.127.146.30 216.127.139.10   I am having a serious issue with customers not being able to login via DialupUsa. Anyone else here using DialupUSA and are you having problems as well? It seems to have started around the time I upgraded to this latest revision and installed this last patch as well.  I had a HD problem which caused my hard drive to fill up and I lost my client defs and had to re-enter them all.  I think I have everything configured correctly but maybe I do not?   I have clients listed as dialupusa1(-4)  216.127.146.27(-30)  secret  RadiusServer Security set to Yes(also tried no) We have Security set to NO Larry   One note is that I am still authing off of WG and all my local NAS's are authing fine.  I'm a bit confused on which end should be called the roamer and what should be called the radiusserver.  I have the wg system entered as a radius server as well with the correct secret.I'm going nuts, and of course it has to happen on the weekend.  Sure wish Vircom offered a per-incident after hours support deal...   Pete