I’m extremely new to SuSE Linux. I wanted to move away from Windows and so I decided to reload my Desktop with SuSE linux.I have had no trouble until now.
I’m trying to connect to my work VPN connection. From my laptop (which unfortunately is Vista) I’m able to connect without any issues. However, when I tried out the KVPN application on my SuSE linux, it just doesn’t work. I get the error : Authentification has failed.
How do I solve this?
As a side note, when I type ping google.com, the packets are received 100% but when I ping my company address, no packets are received. Hope this info is useful.
Cisco Vpn at work? If yes I’m successfully connected and I can help you out. There is a file which needs to be customized to get connected. Let me know.
My vpn is cisco. I have the group password and all, but I’m having a hard time with kvpnc. Kind of irratic behavior. Sometimes it says that it can’t make the script executable, some times it says that the server is not responding. For one fleeting moment, it actually would tell me that my group password was wrong. Once I fixed that, it told me my user password is wrong. Next time I used the same profile, back to non-executable errors and timeouts.
Is it just me, or is this a common issue with kvpnc?
I tried the network manager approach as well, but like another post states, it flashes ‘activating’ so fast that it can’t be doing any real attempt to connect.
I’m game for any ideas, I’d really like to be able to connect without ‘widowifying’ my machine.
On Fri, 2009-12-18 at 00:36 +0000, keyBangingMonkey wrote:
> My vpn is cisco. I have the group password and all, but I’m having a
> hard time with kvpnc. Kind of irratic behavior. Sometimes it says that
> it can’t make the script executable, some times it says that the server
> is not responding. For one fleeting moment, it actually would tell me
> that my group password was wrong. Once I fixed that, it told me my user
> password is wrong. Next time I used the same profile, back to
> non-executable errors and timeouts.
>
> Is it just me, or is this a common issue with kvpnc?
>
> I tried the network manager approach as well, but like another post
> states, it flashes ‘activating’ so fast that it can’t be doing any real
> attempt to connect.
>
> I’m game for any ideas, I’d really like to be able to connect without
> ‘widowifying’ my machine.
>
>
Any reason why you can’t call vpnc from the command line?
I had given it a quick try. Built the config file and ran it. It kept saying that the host didn’t resolve to anything where when I run it from kvpnc it is able to resolve to an IP. I’ll have to give it another shot though. I didn’t give that solution (command line call to vpnc) a whole lot of effort.
I have the next problem on OpenSuse 11.2:
I needed to connect remote to my computer at work. I’ve installed AT&T client (agnclient-1.0-2.0.1.3003.i386.rpm + prerequisites). All is working fine, I can connect to my computer from work using KRDC. But I have the next problem:
From that point on I can browse the internet only after I start AT&T client.
Probably AT&T client broke the ip table, but I really don’t know how to fix this. It is interesting that Skype works with/without AT&T client running. But it is the only one.
I used AT&T client with OpenSuse 11.0 and I didn’t have this problem.
I’m not a linux specialist. I started to use linux in order to see how Java programs look/run on linux systems (I’m a java programmer).
Has somebody any idea how to fix this?
Thank you for any suggestion.
Well, probably your /etc/resolv.conf file has been changed – which normal behavior. Because you’ve shut down the system without ending the AT&T connection first (this is an assumption), you did not reinstate your old DNS settings.
This is a reply to suse_aficionado who open the thread initially and which I think was hijacked and changed into a different issue.
I connect via Cisco vpn and here are the steps I perform.(Note that I never tried to use kvpnc and I call via terminal).
I su to root and run vpnc(at the end I disconnect via vpnc-disconnect)
I have a configuration file customized in /etc/vpnc/default.conf which have these mandatory 4 lines:
IPSec gateway - your gateway name
IPSec ID - your company id for vpn
IPSec secret - cisco vpn password
XAuth username -your lan id at work
As soon as you issue the command vpnc you are asked for the password which is the prefix you have + the numeric number on the token at that moment (I assume this is generally the rule for CiscoVPN but I don’t know if that’s your case)
As soon as you are connected successfully you’ll receive a message. From this point on you are part of your work network(and beware that any transaction/onnection from then on might be scrutinized by the your network security and the policies for your company, so watch out what you browse and what you download until you disconnect). You don’t have to connect to your machine (via let’s say remote desktop to do work, or use that browser). You can browse directly with your local browser on your machine and that’s where some people would fail to understand what are they doing wrong since they are not connected to their remote machine. I just wanted to emphasize on this, hopefully i didn’t over do it.
I never had problems connecting since day 1, but i never used the kvpnc. Kde it’s a great distro but is still buggy and i encountered issues with it on other applications, so if i can run something from the terminal i would do it, before using the gui for it. (knetwork, kde3 are other few things which are giving me a hardtime sometimes).
Let me know if you need any other details.
Have fun!
I have had to change my resolv.conf nameserver DNS to access the net. Now vpnc: no response from target is the reply to vpnc.
I guess I must now adda line to etc/sbin/vpnc.conf for the mode; something like NAT traverse mode cisco-vdp but this is unknown and tells me to use Natt none force-natt cisco-udp which then states as an unknown configuration.
can anybody give me the code for line 6 in vpnc.conf or should I alter resolv.conf?:’(:’(
I found a solution to my problem, though I don’t like it very much. I just finished configuring a default.conf file inside /etc/vpnc and was able to connect from the command line… I’d like to connect through the GUI though… I’ll keep trying and post if succeed. Thanks!
I finally got things to work the way I want. The key thing was to enter the decoded password group in the configuration (a piece of data I didn’t have but I got it from cisco vpnclient password decoder