CLEANACCESS Archives

October 2006

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
William Doyle <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Thu, 26 Oct 2006 14:25:40 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (73 lines)
DNS is fine.



At 02:03 PM 10/26/2006, you wrote:
>Maybe the client has a stale DNS entry?  Can you do an nslookup from the
>client you are testing on?  Can you also do a reverse lookup on
>xxx.xxx.53.xxx?
>
>-Rajesh.
>
>-----Original Message-----
>From: Cisco Clean Access Users and Administrators
>[mailto:[log in to unmask]] On Behalf Of William Doyle
>Sent: Thursday, October 26, 2006 12:57 PM
>To: [log in to unmask]
>Subject: Re: cert problem
>
>Yes, I do.
>
>Interestingly, in my earlier installation the url of the captured web
>login page would be
>https://computer.berkeley.edu/auth/perfigo_weblogin...etc but now it is
>https://xxx.xxx.53.xxx/auth/..etc.  And, the .53 in the third octet
>should be .253. I checked the IPs of the pair and they have the proper
>IP
>
>At 12:35 PM 10/26/2006, you wrote:
> >Bill,
> >
> >If you try a weblogin from IE, do you get a similar security
> >warning/error or not?
> >
> >-Rajesh.
> >
> >-----Original Message-----
> >From: Cisco Clean Access Users and Administrators
> >[mailto:[log in to unmask]] On Behalf Of William Doyle
> >Sent: Thursday, October 26, 2006 12:11 PM
> >To: [log in to unmask]
> >Subject: cert problem
> >
> >Goo Day,
> >
> >Sorry if this is a duplicate post.
> >
> >I upgraeded to 4.0.3 and am having a problem with certificates. I
> >install ed a certificate from a root authority and everthing seems
>fine.
> >CCA indicat es that the certificate domain is computer.berkeley.edu.
> >
> >When attempting to log on using the agent I receive a cert warning
> >statin g that the cert is issued by a root authority, the time is
> >correct, but the
> >
> >name ia wrong. The cert details indicate the cert was issued to
> >computer.berkeley.edu. An nslookup of computer.berkeley.edu returns the
> >
> >service IP of the failover pair.
> >
> >While I have failed logging in with a couple of different error
> >messages,
> >
> >most of the time I can successfully log on. However, after logging on,
> >I
> >
> >
> >have consistently been unable to log off.
> >
> >Any ideas appreciated
> >
> >Bill Doyle

ATOM RSS1 RSS2