02-17-2009
Network connection problem in unix
I have a network connection problem in unix. I am trying to access to LAN in unix but unfortunately it doesn't work. For example, if I ping from Unix to windows it says 'the network is unreacable'. Also, I can't ping in windows to unix.
I would be glad if someone could help me.
Thanks.
Fatih
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Changed from a broken Switch to a working HUB everyting else in my network is ok after the change but not my RS/6000! It refuses to get connected, get time out on Pings both ways - strange?
Could it be some problem with ARP?:confused: (2 Replies)
Discussion started by: jolun
2 Replies
2. UNIX for Dummies Questions & Answers
Having problem in connecting my gui java program to postgreaql database. I first used setenv classpath /home/share/postgresql/java/postgresql.jar:proj1, where proj1 is my folder conatining all java and class file, to set classpath. Then javac *.java. Then java proj1.Login. It gives me... (2 Replies)
Discussion started by: uci
2 Replies
3. IP Networking
Dear Member:-
Kindly be I am facing a problem with my open Solaris release b101
1- vi /etc/hostname.reg0
This is my IP address xx.xx.xx.xx
2- vi /etc/netmasks
This is my subnet mask
3- vi /etc/defaultrouter
This is my gateway
4- vi /etc/resolv.conf
This is my DNS written with this way ... (2 Replies)
Discussion started by: dellroxy
2 Replies
4. Solaris
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. Solaris
Hello colleague,
Development department is deploying some applications on solaris machine but hence all connection goes down.
Our all network connection files are correct but we can't connect with our gw. Only we can ping localhost and assigned ip address.
I don't want to reboot for... (4 Replies)
Discussion started by: getrue
4 Replies
6. Linux
Hi, I installed linux Fedora on a virtual machine, but the network connection is not working. All firewalls are off. Any ideas what is the problem? I am using WiFi.
Thanks in advance!
Regards,
Atanas (2 Replies)
Discussion started by: apenkov
2 Replies
7. Solaris
hi,
I'm setting up a home lab and I am having problems keeping my connection open on putty. every time i leave it for about 10 seconds and come back I keep having to re-connect. I'm more of a AIX person and trying to get more fimilar with Sun but some of the commands I am trying to run to diag... (2 Replies)
Discussion started by: vpundit
2 Replies
8. Programming
I have started reading the book Unix Network Programming, Volume 1: The Sockets Networking API. I downloaded all the source code and the readme says I must make the files.
zuro@zuro:~/book/unpv12e$ cd lib
zuro@zuro:~/book/unpv12e/lib$ make
gcc -g -O2 -D_REENTRANT -Wall -c -o... (5 Replies)
Discussion started by: xuro
5 Replies
9. Programming
I have started reading the book Unix Network Programming, Volume 1: The Sockets Networking API. I downloaded all the source code and performed all the steps present in README file.Now when i compile my first program it give the following error.
sainandan@nandan:~/unpv13e/intro$ ./daytimetcpcli... (1 Reply)
Discussion started by: bsainandan
1 Replies
10. Solaris
Hi,
Recently we faced awkward situation where we cannot connect to Oracle DB that hosted in Solaris server intermittently and it timeout eventually. The server seems fine. We can putty to server like normal but when try do prstat, it takes time and come out Please Wait.. for a while. When we go... (1 Reply)
Discussion started by: tharmendran
1 Replies
LEARN ABOUT OPENSOLARIS
ssh-agent
ssh-agent(1) User Commands ssh-agent(1)
NAME
ssh-agent - authentication agent
SYNOPSIS
ssh-agent [-a bind_address] [-c | -s ] [-d]
[command [args]...]
ssh-agent [-c | -s] -k
DESCRIPTION
ssh-agent is a program to hold private keys used for public key authentication (RSA, DSA). ssh-agent is often started at the beginning of a
login session. All other windows or programs are started as clients to the ssh-agent program. Through use of environment variables, the
agent can be located and automatically used for authentication when logging in to other machines using ssh(1). See the System Administra-
tion Guide: Security Services.
If a command line is given, this is executed as a subprocess of the agent. When the command dies, so does the agent.
The agent initially does not have any private keys. Keys are added using ssh-add(1), which sends the identity to the agent. Several identi-
ties can be stored in the agent; the agent can automatically use any of these identities. Use the -l option in ssh-add(1) to display the
identities currently held by the agent.
The agent is run in the user's local host. Authentication data need not be stored on any other machine, and authentication passphrases
never go over the network. However, if the connection to the agent is forwarded over SSH remote logins, the user can use the privileges
given by the identities anywhere in the network in a secure way.
There are two main ways to get an agent setup. Either you let the agent start a new subcommand into which some environment variables are
exported, or you let the agent print the needed shell commands (either sh(1) or csh(1) syntax can be generated) which can be evalled in the
calling shell. Later, use ssh(1) to look at these variables and use them to establish a connection to the agent.
A unix-domain socket is created (/tmp/ssh-XXXXXXXX/agent.pid) and the name of this socket is stored in the SSH_AUTH_SOCK environment vari-
able. The socket is made accessible only to the current user. This method is easily abused by root or another instance of the same user.
The SSH_AGENT_PID environment variable holds the agent's PID.
The agent exits automatically when the command given on the command line terminates.
OPTIONS
The following options are supported:
-a bind_address Binds the agent to the unix-domain socket bind_address. The default is /tmp/ssh-XXXXXXXX/agent.pid.
-c Generates C-shell commands on stdout. This is the default if SHELL indicates that it is a csh style of shell.
-d Debug mode. When this option is specified, ssh-agent will not fork.
-k Kills the current agent (given by the SSH_AGENT_PID environment variable).
-s Generates Bourne shell commands on stdout. This is the default if SHELL does not indicate that it is a csh style of
shell.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
FILES
/tmp/ssh-XXXXXXXX/agent.pid
Unix-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner. The
sockets are removed when the agent exits.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsshu |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
SEE ALSO
ssh(1), ssh-add(1), ssh-keygen(1), sshd(1M), attributes(5)
System Administration Guide: Security Services
SunOS 5.11 17 Nov 2008 ssh-agent(1)