Login or Register to Ask a Question and Join Our Community


UNIX for Dummies Questions & Answers

help with vpn

 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers help with vpn
# 1  
Old 07-07-2005
help with vpn
We have an older model DG Aviion Unix system and we're trying to switch to VPN but we can't talk to the Unix box... can't ping or telnet to it, but we can talk to all our other systems (PC/NT servers).

Is there a network/tcpip setting we're missing? Something we have to change/set, either on the Unix box or the VPN?

Thanks in advance for any help.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Vpn

Hi. Yesterday I installed Solaris 11.3 and I tried to setup a VPN but I didn't find how to make it. I saw the "network manager" where I found the ethernet connection but I didn't find where to add a VPN connection. When I used Debian Linux there was NetworkManagerVPN that with a GUI I... (0 Replies)
Discussion started by: Jena
0 Replies

2. Cybersecurity

VPN Security

Hello Gurus : I had a question about VPN connection . Say for instance i have to connect from my point A to point B (Is the place where i initiate the VPN connection ) . From there i connect to point C (i.e Bank) . My question is this a secure connection . (from point A to C) Thanks... (3 Replies)
Discussion started by: tsbiju
3 Replies

3. Solaris

vpn not connecting

Hi, I have been using using internet explorer on windows for connecting with production server using vpn connection. i want to use same vpn to connect from solaris system to the production server.it is not connecting is there solution (0 Replies)
Discussion started by: malikshahid85
0 Replies

4. UNIX for Advanced & Expert Users

advertisement in vpn

I am looking for a solution to add a web banner in all web page sessions when user is connected through pptp vpn connection. any solution? may be using squid or pptp servers? (1 Reply)
Discussion started by: vansari
1 Replies

5. 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

6. UNIX for Advanced & Expert Users

VPN and then

Hi, I want to work on a remote unix server, then on a windows XP station I have a Forticlient that makes a VPN to the network on which the server is situated. But then I do not know how to work with. In DOS box (cmd BOX) I issue: telnet myserver but It does not know IT. Any idea ? Many thanks. (2 Replies)
Discussion started by: big123456
2 Replies

7. Linux

VPN Solutions

Hello Friends I want to know about VPN Solutions under Linux Please help me :confused: (6 Replies)
Discussion started by: jaibw
6 Replies

8. IP Networking

Vpn

Hi, I have two unix networks connected via VPN via IPsec. I am using snapgear vpn devices at each location. The two devices can ping one another, as well as the unix network behind the respected devices. The unix machines can ping their local vpn devices. However, I am having issues pinging... (1 Reply)
Discussion started by: l8kerboi23
1 Replies

9. UNIX for Dummies Questions & Answers

One VPN question

Hi, My setup is as follows: 1) HeadOffice----->Private subnet: 192.168.0.0 2) Branch1-------->Private subnet: 192.168.200.0 I'm connecting from branch1 to headoffice thru VPN and I'm able to access all PC's except SCO UNIXWARE 7.1.1 box. I have made a search before posting this... (7 Replies)
Discussion started by: tayyabq8
7 Replies
Login or Register to Ask a Question

LEARN ABOUT OSX

talk

TALK(1) 						    BSD General Commands Manual 						   TALK(1)

NAME

     talk -- talk to another user

SYNOPSIS

     talk person [ttyname]

DESCRIPTION

     The talk utility is a visual communication program which copies lines from your terminal to that of another user.

     Options available:

     person   If you wish to talk to someone on your own machine, then person is just the person's login name.	If you wish to talk to a user on
	      another host, then person is of the form 'user@host' or 'host!user' or 'host:user'.

     ttyname  If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
	      name, where ttyname is of the form 'ttyXX'.

     When first called, talk sends the message
	   Message from TalkDaemon@his_machine...
	   talk: connection requested by your_name@your_machine.
	   talk: respond with: talk your_name@your_machine

     to the user you wish to talk to.  At this point, the recipient of the message should reply by typing

	   talk  your_name@your_machine

     It does not matter from which machine the recipient replies, as long as his login-name is the same.  Once communication is established, the
     two parties may type simultaneously, with their output appearing in separate windows.  Typing control-L '^L' will cause the screen to be
     reprinted.  Typing control-D '^D' will clear both parts of your screen to be cleared, while the control-D character will be sent to the
     remote side (and just displayed by this talk client).  Your erase, kill, and word kill characters will behave normally.  To exit, just type
     your interrupt character; talk then moves the cursor to the bottom of the screen and restores the terminal to its previous state.

     Permission to talk may be denied or granted by use of the mesg(1) command.  At the outset talking is allowed.

CONFIGURATION

     The talk utility relies on the talkd system daemon.  See talkd(8) for information about enabling talkd.

FILES

     /etc/hosts      to find the recipient's machine
     /var/run/utmpx  to find the recipient's tty

SEE ALSO

     mail(1), mesg(1), wall(1), who(1), write(1), talkd(8)

HISTORY

     The talk command appeared in 4.2BSD.

     In FreeBSD 5.3, the default behaviour of talk was changed to treat local-to-local talk requests as originating and terminating at localhost.
     Before this change, it was required that the hostname (as per gethostname(3)) resolved to a valid IPv4 address (via gethostbyname(3)), making
     talk unsuitable for use in configurations where talkd(8) was bound to the loopback interface (normally for security reasons).

BUGS

     The version of talk released with 4.3BSD uses a protocol that is incompatible with the protocol used in the version released with 4.2BSD.

     Multibyte characters are not recognized.

BSD
								  August 21, 2008							       BSD