Sponsored Content
Top Forums UNIX for Beginners Questions & Answers VPN Connection Problem using OpenVPN Post 303044668 by hicksd8 on Saturday 29th of February 2020 04:58:39 PM
Old 02-29-2020
You're not saying whether there are any errors logged by the system. It would be really useful if you can post what the system log says when the VPN connection fails.

Being a Fedora distro it won't have the typical syslog file but I believe that you can translate the digital log live via a terminal using

Code:
sudo journalctl -f

(The -f switch here means 'follow')

After opening a terminal and running this command try to connect to the VPN. Watch the terminal to see if it tells you the reason for the failure.
This User Gave Thanks to hicksd8 For This Post:
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Testing VPN Connection

Hi All: I need a script that can be timed to run every half hour to an hour to run a traceroute through a VPN to test that a connection is still up from a Win XP system. Which would be the best, C++ or Perl and what are some good resources to look at. (If anyone has a script to do this... (1 Reply)
Discussion started by: maxhewitt
1 Replies

2. Linux

vpn problem

Trying to connect to my companies VPN with vpnc but I keep getting an error that the target failed to respond. I run wireshark and see that my host sends out a few ISAKMP packets but gets no response and gives up. Any ideas what can cause this to happen? Is there someway that UDP traffic could... (0 Replies)
Discussion started by: osulinux
0 Replies

3. IP Networking

VPN Connection

Hello, I have question about VPN connection thats, I have two networks 1-Office Network 2-Home Network both are connected to internet i have in Office network PPTP VPN Server with real or static ip and on the home network all clients working with local ip Now , I need to connect to... (3 Replies)
Discussion started by: LinuxCommandos
3 Replies

4. Solaris

Solaris 10 ftp connection problem (connection refused, connection timed out)

Hi everyone, I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies

5. SCO

Printing to Windows 7 using Samba 2.0.3 via VPN connection to SCO 3.2v5.0.6

I would like to know if anyone has a way to PRINT TO a printer attached to a Windows 7 PC, from SCO, while logged in via a VPN connection. I am able to attach to a Samba share on the SCO server for files while attached to the VPN, so I know my Samba is workling - but my print jobs return: ... (2 Replies)
Discussion started by: tbb999
2 Replies

6. IP Networking

Cisco VPN pcf and OpenVPN

I was given my pcf file to login to work from home and wanted to use OpenVPN instead of the Cisco VPN client software. Can I use this pcf file with OpenVPN? I attempted to use vpnc: http://wiki.centos.org/HowTos/vpnc but it just times out ?? (2 Replies)
Discussion started by: metallica1973
2 Replies

7. IP Networking

Cisco VPN server and client - connection drop

I have a Cisco 1841 router configured as Easy VPN Server. Here is the configuration of the router: Cisco# Cisco#show running-config Building configuration... Current configura - Pastebin.com I have a Centos 5.7 server with installed Cisco VPN client for Linux. The client successfully... (0 Replies)
Discussion started by: rcbandit
0 Replies

8. Cybersecurity

VPN Initial Connection Problem

Hey everyone. I have a problem, but it may be my lack of understanding that is the cause. Ok so I attend a technical school, and needless to say there's a lot of wannabe hackers, pranksters and what not. So from my laptop I'd like to connect to the wireless AP's around campus, but security is a... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies

9. IP Networking

Internet connection single interface through vpn

Hi. Can you please help me with a routing problem? There are 2 networks: 192.168.10.0/24 (eth0) 192.168.11.0/24 (eth0:1) The default gateway is 192.168.10.1 iPv4 routing is already enabled and working. With vpnc I've built up an VPN connection and can access my home network... (0 Replies)
Discussion started by: tschmi
0 Replies
LLOGIN(1)						      General Commands Manual							 LLOGIN(1)

NAME
llogin - Connect to a LAT service SYNOPSIS
llogin [options] service Options: [-dvcpblhQ] [-H node] [-R port] [-n name] [-w password | -W] [-q quit char] DESCRIPTION
llogin connects your terminal to a LAT service via latd, the service name must be known to latd for this to work. OPTIONS
-d Shows learned services. This is the same as latcp -d -l -d -v Verbose form of -d. -v without -d is ignored. -H <node> Remote nodename. If the service is advertised by more than one node and you want to connect to a particular node then use this switch. By default you will be connected to the node with the highest rating. -R <port> Connect to a specific port on (usually) a terminal server. This is the port NAME on the server and not the port number. -c Do not convert typed LF to CR. By default the enter key generates LF and llogin converts it CR as it is the most generically useful translation. This switch will cause the enter key to send LF instead. Occasionally useful for connecting to Unix consoles. -b Convert typed DEL to BS. By default the DEL key (keyboard, top right usually) send DEL (ASCII 0x7f) to the remote system. This switch will cause the DEL key to send BS (ASCII 8) instead. Useful for some Unix systems connected via terminal servers. -l Convert output LF to VT. By default LF output is sent as CRLF which can cause output formatting problems. Changing this to VT should preserve the output formatting on most devices or terminal emulators. -q <char> Change the quit character. By default CTRL-] will quit the terminal session. Entering a character after -q will cause CTRL-<char> to be the quit character for that session. -q0 will disable the quit character. If you use the latter, make sure you are connecting to a service that will disconnect you when you log out or you will have to kill llogin from another session to get out of it! -Q Tells latd that the service you are connecting to is queued service and not a normal login service or port service. Unfortunately latd cannot tell whether a remote service needs to be queued or not so the onus is on the user to specify this switch when connect- ing to a queued service. -n <name> Sets the local connection name. By default this will be your local TTY name. In most cases this simply affects the display of the terminal on the remote end so you shouldn't need to change it. -w <password> Sends the password for the service. Only needed for services that require a password for access. If the password given is "-" then you will be prompted for a password and it will not be echoed. This avoids having passwords visible on the screen. -W Prompts for the service password. This is the same as -w- (see above). -p Tells llogin to connect to the device named instead of a LAT service. This would usually be a /dev/lat pseudo-terminal but could be any other device you like really. This switch does not make the program useful as a terminal program because there is no way to set any serial parameters, nor am I going to add them. This is just a convenient way to use the /dev/lat ports without the overhead of programs such as minicom. -h Displays a brief usage description. This is the same as invoking llogin without any parameters at all. SEE ALSO latcp(8), latd(8) LAT utilities January 3 2002 LLOGIN(1)
All times are GMT -4. The time now is 04:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy