|
Larry,
Yeah...I have 1645 and 1646 and
just got off the phone with DialupUsa and they said that's what they have on
their end as well. He verified that the ip's I listed were correct but did
say that 27 was not being used right now.
I'm going crazy...Are their Ip's supposed to be
listed as a Radius Server or as Roamer server?
Pete
----- Original Message -----
Sent: Saturday, September 11, 2004 4:02
PM
Subject: [VOPRadius] New Update Available
: Update 7 for VOP Radius 4.0 228
At 03:45 PM 9/11/2004, you
wrote:
Okay,
it's saying Timeout Reached , removing Username. It's like I can hear
DialupUsa's server, but they can't hear me. I removed all my
access-lists from my router to make sure something wasn't getting blocked
there...still no go.
Do you have the correct ports
set for Acct and Auth ?
Larry
Pete
- ----- Original Message -----
- From: Sysop
- To: [EMAIL PROTECTED]
- Sent: Saturday, September 11, 2004 3:41 PM
- Subject: [VOPRadius] New Update Available : Update 7 for VOP
Radius 4.0 228
- According to Dialupusa's logs, they aren't
getting a response of any kind. I can see the users come on, the NAS
be created in my Worldgroup audit trail, and on the Vprrs users online
screen. On the Users Online Screen I will see the user come in in
Auth State first, then go to Start, then to End..and that's it. No
errors in log files, no nothing. Gonna have to crank the logs
up to debug levels I guess...
- Pete
- ----- Original Message -----
- From: Paul Moore
- To: [EMAIL PROTECTED]
- Sent: Saturday, September 11, 2004 3:20 PM
- Subject: [VOPRadius] New Update Available : Update 7 for VOP
Radius 4.0 228
- Is anything showing up in your logs? Are you stripping realm names off
of the users?
- Paul
- Sysop wrote:
- 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)
- 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
- ----- Original Message -----
- From: Customer
Support
- To: [EMAIL PROTECTED]
- Sent: Friday, September 10, 2004 1:08 PM
- Subject: [VOPRadius] New Update Available : Update 7 for VOP
Radius 4.0 228
- Dear Customers,
- This email is directed to all customers
running VOP Radius Version 4.0.
- Vircom has released a new update/patch for
VOP Radius 4.0 Build 228. The new issues fixed in this patch
include:
- * A warning to customers to customers that
the ODBC Data type for the "Analog" and "Digital" fields should be set
to INTEGER rather than BINARY (see readme.txt for more
information)
- * Fixed SQL sample scripts to create
Analog-Access and Digital-Access record
- as integer.
- * Fixed Microsoft Access sample database creating Analog-Access and
Digital-
- Access record as integer.
-
- * Fixed VOP Radius help file to document
Analog-Access and Digital-Access
- record as integer.
- ********
- There may be some confusion because a patch
called "Update6" was never released under the download section. There is
no need to worry about this because Update7 will contain all the fixes
done in Update6 (all the updates are cumulative). The fixes made in
Update6 included:
- - Fixed SQL support for Analog-Access
and Digital-Access special attributes.
- Some SQL server would return
values else than 0 and 1.
-
- - Fixed VOP Radius MMC console.
- VOP Radius MMC console was not
working using UDP.
- VOP Radius MMC console was not
working properly with 4.0.228 server.
-
- - Fixed User List file format
- User list file format now
friendly reader (stretched over 132 columns).
-
- - Fixed Time-Of-Day special attribute.
- A bug has been inserted in
4.0.228 which prevented use of Time-Of-Day.
- ********
- Vircom highly recommends ALL customers to
apply the Update7 patch because there are fixes that can prevent
authentication problems (e.g. Fix for Analog and Digital Access fields)
- The patch is available on our website under
the "My Vircom" section. You will need to use your license key to bypass
the security on the webpage. Next, under the download link for VOP
Radius 4.0 there will be a link for "Update 5 for Radius 4.0". The
download will include a ZIP file with the installation package and
readme file.
- Note: Again, all updates are cumulative
(i.e. Update7 will include all the fixes incorporated into Updates
1,2,3,4,5, and 6).
- The install instructions are posted in the
Readme.txt file, but I have written them here as well for
convenience:
- 1) Make sure version 4.0.228 is
installed
- 2) Stop VOP Radius and close the console
- 3) Launch VPRRS228.5.EXE installation package.
- 4) Read the Readme.txt file.
- 5) Start VOP Radius
- 6) Confirm under NT Event Viewer --> Application Log that the
service started ok
- Vircom Technical Support
- Phone: (514) 845-8474
- Email: [EMAIL PROTECTED]
|
