LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Security
User Name
Password
Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.

Notices

Reply
 
Search this Thread
Old 04-18-2013, 01:56 AM   #1
navneethr
Member
 
Registered: Jan 2010
Posts: 69
Blog Entries: 1

Rep: Reputation: 16
Unable to connect using vpnc but Window user can do it.


I am using vpnc on Fedora to get into a VPN however I am facing problems with the parameters that need to be supplied.


Enter IPSec gateway address: This address is known
Enter IPSec ID for : I do not know what goes here
Enter IPSec secret for : I do not know what goes here
Enter username I know what goes here
Enter password for - I 0know what goes here

and hence I get an error.

However another person can connect into the VPN when they use Windows without having to supply the values for
Enter IPSec ID for : I do not know what goes here
Enter IPSec secret for : I do not know what goes here

Does this mean that these values are residing somewhere on a file on the Windows machine. Can someone let me know where that file will be and how to retrieve those values?

For Fedora: Do I need to install or copy some file from the window machine here?

Is there an alternative to the vpnc command to get into the VPN which will just ask me for the username and password. Right now security is not so important. Getting into the network via VPN is most important.

Awaiting your reply/suggestion. Will appreciate it very much.
 
Old 04-19-2013, 04:28 PM   #2
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,401

Rep: Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114
Save yourself a lot of time here, and ... talk with the party that's responsible for maintaining the other side of the connection. They will have access (a) to the parameters and secrets which might be "automagically supplied to" the Windows folks, and (b) most-importantly, the server-side console logs that will provide necessary diagnostic information.

They can, first, tell you exactly what to supply. Then, they can tell you a bit about what you're doing wrong. And, by design, you'll find that you really can't get anywhere without that. You see, secure systems like VPN are expressly designed not to divulge anything to the ("untrusted!!") person who shows up a'knockin' at their door. If the credentials supplied are exactly correct, the lock opens. If not, the response (by design!) gives no clue.

(Rest assured that thousands of folks right now are quite-successfully using these Linux tools to make VPN connections. But the process of successfully making a VPN connection is designed to be obtuse.)

Last edited by sundialsvcs; 04-19-2013 at 04:30 PM.
 
Old 04-21-2013, 04:27 AM   #3
navneethr
Member
 
Registered: Jan 2010
Posts: 69
Blog Entries: 1

Original Poster
Rep: Reputation: 16
Thanks very much. I do understand. I will do the same. Have a good day.
 
Old 04-21-2013, 11:20 PM   #4
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,401

Rep: Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114
One more thing to note ... some of VPN's messages are just "pure crap." Even on the server-log side, they were written by programmers in programmer terms such that they basically don't give any useful information at all about the nature of the actual problem.

Classic example I had of this, when trying to connect, was "self-signed certificate in chain." Or something to that effect. And, yes, the server certificate (which was being used for many successful connections) was indeed self-signed ... but that was not the actual problem. It turns out that the person-in-charge had actually sent me the wrong ca.crt file ... one in which the "state" field was "Pa" not "PA." (Therefore, the cert did not "match.") The message given, while technically correct in terms of describing the outcome of the connection attempt, gave no useful diagnostic information to any of us that would point to what was actually wrong ... not to the party trying to connect, and not to the back-end folks who were entitled to know details. There are a lot of "WTFs" like that in this territory (regardless of implementation).

Last edited by sundialsvcs; 04-21-2013 at 11:21 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] connect to a vpn connection using vpnc someshpr Linux - Software 2 11-16-2010 04:56 PM
Unable to start any window managers as user (fine as root) Pscylo Slackware 2 04-12-2009 12:07 PM
vpnc as a normal user watcher69b Linux - Networking 1 06-05-2008 02:34 PM
unable to connect with samba from window farnaw4u Linux - Networking 2 11-21-2006 11:21 PM
user unable to connect to X(other then the log'd one) jabka Linux - General 4 07-07-2006 03:59 AM


All times are GMT -5. The time now is 05:20 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration