FYI- If you run the client on a 2003 machine, there is no code to enable
checks. Better hope some of our more savvy students don't hear about
that!
>>> [log in to unmask] 6/24/2005 2:33:05 PM >>>
OK - It's a browser issue. After going through the 3.5.1 install, I
just
couldn't believe 2 releases would have such glaring issues so I
accessed
it from a different machine, and it all seems to be there now! I was
using Server 2003, and "parts" of pages were simply not there.
Accessing
it from Windows 2000, all the missing boxes are back where the manual
says they should be! Whew...
Jeff
-----Original Message-----
From: Hague, Jeff
Sent: Friday, June 24, 2005 2:21 PM
To: [log in to unmask]
Subject: Re: [PERFIGO] 3.5.2 not ready for prime time?
A clean install 3.5.1 exhibits the same "quirks". I guess Ill drop
back
to 3.4.0 and see what happens there.
BTW - the error when trying to add a VLAN id that I outlined below is
actually when adding a DHCP scope, not when adding a managed subnet -
oops...
Jeff
-----Original Message-----
From: Hague, Jeff
Sent: Friday, June 24, 2005 12:28 PM
To: [log in to unmask]
Subject: [PERFIGO] 3.5.2 not ready for prime time?
I have a clean install of CCA 3.5.2 (not patched to 3.5.2.1 yet), and
it
seems to be missing a few things. For instance, when setting up an NT
authorization server, the box to enter the domain name is missing.
Also,
when setting up a traffic control policy, category set to IP, no TCP
or
UDP option is available. Another strange thing is when adding a
managed
subnet that is associated with a VLAN id, the box to enter the VLAN id
is present, but I can not get my cursor in to it. I found that
clicking
apply, and waiting for the page to refresh with an error, allows you
to
enter the VLAN id.
Needless to say, I can not get CCA 3.5.2 to work. It seems to pass
dhcp
and dns in the unauthenticated role, but never redirects to the web
login page. Could my install simply have gotten corrupted or are
others
experiencing similar issues?
I would like to get the latest version set up so I have plenty of time
to configure it and test - should I drop back to 3.5.0 or 3.4?
How would that affect my upgrade options once these issues are
resolved?
Thanks for any insight!
Jeff Hague
MCSE
Network Manager
Randolph-Macon College
Ashland, VA
|
