Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN

Status
Not open for further replies.

Riconsuave

IS-IT--Management
Apr 26, 2003
2
CA
I just installed client 4.65 for XP but when I'm trying to connect I'm getting an error
"login failure due to driver failure"
Any knows how to by pass this?
thanks in advance

 
client 4.65 of what?

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
[/sub]
 
oops!!
The SW is Nortel Extranet client 4.65 for VPN,
I've also installed the Entrust part, and I get another error "you are working offline because your Entrust Directory was unavailable ".
do you have any idea why?
thanks in advance.
 
Any out there know best way to monitor remote VPN sites via SNMP. My routers are cisco 2611. I'm reading on IPSEC/ISAKMP FLOWMONITOR. I would like snmp traps to tell me when vpn tunnels go down.... I'm not sure if the payloads and tunnels independent of each other.. From what I read so far tunnels could be up but payload could NOT get across..
If anyone has over come this challege I would appreciate it the lesson.

Thanks,
nXosi
 
nXosi, that is off-topic, please make you own post.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
[/sub]
 
I'm getting the same error message using the Nortel client 4.65.

Login Failure due to driver failure

It worked fine on a vanilla install of WindowsXP so I'm suspicious of security settings apllied via a template.

Anyone have any suggestions?
 
In the instances that I have seen this error, it was caused by the client being installed by a user who was not a local administrator.
 
The client was installed properly using an account with adminsitrator privileges. However, we solved this issue by removing the NT AUTHORITY\INTERACTIVE Account from the Network Configuration Operators Local Group...

Bizarre, and it took ages to troubleshoot, but that was the cause and fix for us. Incidentally, adding the account AFTER the install was fine... the client would work no problem...

Cheers, Dyce
 
Dyce,

> The client was installed properly using an account with
> adminsitrator privileges. However, we solved this issue by
> removing the NT AUTHORITY\INTERACTIVE Account from the
> Network Configuration Operators Local Group...

Can you explain how to do this? I've been going around with this issue for months trying various things. Today, I tried to upgrade XP with no luck. My network admin says the only way to resolve this is to reformat my driver, reinstall windows.

I'd greatly appreciate the help.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top