Sponsored Content
Full Discussion: Telnet solaris error
Operating Systems Solaris Telnet solaris error Post 302594107 by admin_xor on Monday 30th of January 2012 12:40:11 PM
Old 01-30-2012
What's the network address and subnet mask of the Host-Only network? Have you assigned an IP to the Solaris VM in the same subnet? If not, you will not be able to ping the VM from the host machine!!

As I told earlier, this is not an issue with the Solaris VM. You just need to check network settings in the VMWare Virtual Network Editor. If you are not sure how to edit those settings, enable dhcp in the Solaris VM and check the IP address assigned to it. Later you can assign static IP in that particular subnet.

Quote:
192.168.1.5 vmware ip (what it shows in windows 7) 192.168.31.0 and windows 7 ip is 192.168.1.2 . Default gateway: 192.168.1.1
IPs are meaning less without the subnet mask. Assumming that you are using the default 24 bit Class C subnet mask, your Solaris VM is clearly on a different subnet than the host machine. They both have to be on 192.168.1.0/24 subnet according to what you have posted.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Telnet into Solaris 8

How can I set my Solaris 8 machine to allow a telnet session from an IP address that is outside the network that the machine sits on? I can ping the address of the Soalris 8 box from the outside, but I cannot telnet into it, it doesn't allow the connection. (1 Reply)
Discussion started by: Ask Me
1 Replies

2. UNIX for Dummies Questions & Answers

Telnet into Solaris 8 box

I am new to Unix. What file do I need to edit so that I can telnet to Solaris 8. I recieve this message everytime I try to telnet. It allows me to LOGIN but kicks me out with this same message. SunOS 5.8 login: root Password: Not on system console (2 Replies)
Discussion started by: newbie05
2 Replies

3. UNIX for Dummies Questions & Answers

solaris telnet idle timeout

I have put TMOUT=1800;export TMOUT in the /etc/profile, put it does not work, by the way the root default shell is sh. but I wana every one including root to terminate the session after setting idle for 1800 seconds. thank for the help. (1 Reply)
Discussion started by: kahn630
1 Replies

4. Solaris

disable telnet on Solaris

All - would you please some one help me to disable telnet on Solaris? /etc/inetd.conf Thanks :confused: (11 Replies)
Discussion started by: March_2007
11 Replies

5. Solaris

HP-UX telnet to Solaris

Hi, i have a strange problem. i have a HP-UX which is used to telnet to two solaris machine via port 11000. On the solaris machines, there's an application that sends a series of ascii character separated by LF over to the the HP-UX. The problem is that when the HP-UX connects to solaris A,... (2 Replies)
Discussion started by: xenomage
2 Replies

6. UNIX for Dummies Questions & Answers

Help with telnet using putty on solaris 10 x86

Hi ... I am totally new to unix ... I just installed solaris 10 and internet is working. Everytime I try to telnet from my windows xp using Putty to solaris as root user, putty opens the command prompt window and close right away. I also tried with ssh using Putty and I got a message "Using... (2 Replies)
Discussion started by: glieu
2 Replies

7. Solaris

issue regarding telnet on solaris(9 version)

hi this is hrushi i have issue regarding solaris(9 version) when i telnet from solaris to linux machine it displaying message like connection closed by forine host ...when i telnet from linux to solaris its working fine ...help me its urgent and i'm new to solaris 9 (2 Replies)
Discussion started by: ghrushi84
2 Replies

8. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

9. Solaris

Not able to install telnet on Solaris 11

Hi Solaris 11 Guru, I am not able to install telent on Solaris 11 with the following error as root: uname -a SunOS servername 5.11 11.2 i86pc i386 i86pc pkg install /service/network/telnet pkg: 0/1 catalogs successfully updated: Unable to contact valid package repository Encountered... (3 Replies)
Discussion started by: gjackson123
3 Replies
IPSEC_EROUTE(5) 						  [FIXME: manual]						   IPSEC_EROUTE(5)

NAME
ipsec_eroute - list of existing eroutes SYNOPSIS
ipsec eroute cat/proc/net/ipsec_eroute OBSOLETE
Note that eroute is only supported on the classic KLIPS stack. It is not supported on any other stack and will be completely removed in future versions. On the mast stack, use ipsec policy, on the netkey stack, use ip xfrm DESCRIPTION
/proc/net/ipsec_eroute lists the IPSEC extended routing tables, which control what (if any) processing is applied to non-encrypted packets arriving for IPSEC processing and forwarding. At this point it is a read-only file. A table entry consists of: + packet count, + source address with mask and source port (0 if all ports or not applicable) + a '->' separator for visual and automated parsing between src and dst + destination address with mask and destination port (0 if all ports or not applicable) + a '=>' separator for visual and automated parsing between selection criteria and SAID to use + SAID (Security Association IDentifier), comprised of: + protocol (proto), + address family (af), where '.' stands for IPv4 and ':' for IPv6 + Security Parameters Index (SPI), + effective destination (edst), where the packet should be forwarded after processing (normally the other security gateway) together indicate which Security Association should be used to process the packet, + a ':' separating the SAID from the transport protocol (0 if all protocols) + source identity text string with no whitespace, in parens, + destination identity text string with no whitespace, in parens Addresses are written as IPv4 dotted quads or IPv6 coloned hex, protocol is one of "ah", "esp", "comp" or "tun" and SPIs are prefixed hexadecimal numbers where the prefix '.' is for IPv4 and the prefix ':' is for IPv6 SAIDs are written as "protoafSPI@edst". There are also 5 "magic" SAIDs which have special meaning: + %drop means that matches are to be dropped + %reject means that matches are to be dropped and an ICMP returned, if possible to inform + %trap means that matches are to trigger an ACQUIRE message to the Key Management daemon(s) and a hold eroute will be put in place to prevent subsequent packets also triggering ACQUIRE messages. + %hold means that matches are to stored until the eroute is replaced or until that eroute gets reaped + %pass means that matches are to allowed to pass without IPSEC processing EXAMPLES
1867 172.31.252.0/24:0 -> 0.0.0.0/0:0 => tun0x130@192.168.43.1:0 () () means that 1,867 packets have been sent to an eroute that has been set up to protect traffic between the subnet 172.31.252.0 with a subnet mask of 24 bits and the default address/mask represented by an address of 0.0.0.0 with a subnet mask of 0 bits using the local machine as a security gateway on this end of the tunnel and the machine 192.168.43.1 on the other end of the tunnel with a Security Association IDentifier of tun0x130@192.168.43.1 which means that it is a tunnel mode connection (4, IPPROTO_IPIP) with a Security Parameters Index of 130 in hexadecimal with no identies defined for either end. 746 192.168.2.110/32:0 -> 192.168.2.120/32:25 => esp0x130@192.168.2.120:6 () () means that 746 packets have been sent to an eroute that has been set up to protect traffic sent from any port on the host 192.168.2.110 to the SMTP (TCP, port 25) port on the host 192.168.2.120 with a Security Association IDentifier of tun0x130@192.168.2.120 which means that it is a transport mode connection with a Security Parameters Index of 130 in hexadecimal with no identies defined for either end. 125 3049:1::/64 -> 0:0/0 => tun:130@3058:4::5 () () means that 125 packets have been sent to an eroute that has been set up to protect traffic between the subnet 3049:1:: with a subnet mask of 64 bits and the default address/mask represented by an address of 0:0 with a subnet mask of 0 bits using the local machine as a security gateway on this end of the tunnel and the machine 3058:4::5 on the other end of the tunnel with a Security Association IDentifier of tun:130@3058:4::5 which means that it is a tunnel mode connection with a Security Parameters Index of 130 in hexadecimal with no identies defined for either end. 42 192.168.6.0/24:0 -> 192.168.7.0/24:0 => %passthrough means that 42 packets have been sent to an eroute that has been set up to pass the traffic from the subnet 192.168.6.0 with a subnet mask of 24 bits and to subnet 192.168.7.0 with a subnet mask of 24 bits without any IPSEC processing with no identies defined for either end. 2112 192.168.8.55/32:0 -> 192.168.9.47/24:0 => %hold (east) () means that 2112 packets have been sent to an eroute that has been set up to hold the traffic from the host 192.168.8.55 and to host 192.168.9.47 until a key exchange from a Key Management daemon succeeds and puts in an SA or fails and puts in a pass or drop eroute depending on the default configuration with the local client defined as "east" and no identy defined for the remote end. 2001 192.168.2.110/32:0 -> 192.168.2.120/32:0 => esp0xe6de@192.168.2.120:0 () () means that 2001 packets have been sent to an eroute that has been set up to protect traffic between the host 192.168.2.110 and the host 192.168.2.120 using 192.168.2.110 as a security gateway on this end of the connection and the machine 192.168.2.120 on the other end of the connection with a Security Association IDentifier of esp0xe6de@192.168.2.120 which means that it is a transport mode connection with a Security Parameters Index of e6de in hexadecimal using Encapsuation Security Payload protocol (50, IPPROTO_ESP) with no identies defined for either end. 1984 3049:1::110/128 -> 3049:1::120/128 => ah:f5ed@3049:1::120 () () means that 1984 packets have been sent to an eroute that has been set up to authenticate traffic between the host 3049:1::110 and the host 3049:1::120 using 3049:1::110 as a security gateway on this end of the connection and the machine 3049:1::120 on the other end of the connection with a Security Association IDentifier of ah:f5ed@3049:1::120 which means that it is a transport mode connection with a Security Parameters Index of f5ed in hexadecimal using Authentication Header protocol (51, IPPROTO_AH) with no identies defined for either end. FILES
/proc/net/ipsec_eroute, /usr/local/bin/ipsec SEE ALSO
ipsec(8), ipsec_manual(8), ipsec_tncfg(5), ipsec_spi(5), ipsec_spigrp(5), ipsec_klipsdebug(5), ipsec_eroute(8), ipsec_version(5), ipsec_pf_key(5) HISTORY
Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs. [FIXME: source] 10/06/2010 IPSEC_EROUTE(5)
All times are GMT -4. The time now is 05:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy