telnet from Solaris to Solaris and telnet from PC to Solaris
I have got a problem here. I reload Solaris 2.6 OS into my SunUltra1 and 2 machine, and update the latest patches downloaded from http://www.sunsolve.sun.com.
Sun Machine
----------------
Everything is fine, the system is on my network and user can log in and start with their application remotely from my NFS.
But when I want to telnet to another machine using the terminal window, I have this message
Code:
jennifer_istanbul11>telnet istanbul12
passwd: (my passwd)
Not on system console
jennifer_istanbul11
All my new loaded machine with hostname istanbul?? have theis problem, wherelse my NFS (fsisun-2) has no problem.
PC Machine (1)
-------------------
Code:
Start > Accessories > telnet
Connect > xxx.xx.xxx.xx
SunOS 5.6
Login : (xxxx)
password : (xxxx)
Not on system console
PC Machine (2)
-------------------
From MS-Dos Prompt
Code:
C:\>telnet xxx.xx.xxx.xx
The telnet windows appears
Code:
SunOS 5.6
Login : (xxxx)
password : (xxxx)
Not on system console
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)
Hi,
I have been facing a telnet problem with our SunOS 5.7 box. Initially we were facing porblems in login both from the console as well as through telnet. The machine was hard-booted after which login from console is possible, but telnet connection is not.
The error that is displayed is... (1 Reply)
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)
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)
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)
Dear All,
I need help on allow/disallow OS user to telnet to specific IP address from client side?
I have one Solaris 10 machine, I will permit OS user to telnet to specific IP address. (5 Replies)
Hi all,
I want to telnet/ssh my solaris 10 which was installed in VMware and my host OS is windows 7. I have set the ip address properly in /etc/hosts, /etc/netmasks, /etc/defaultrouter. But when i try to connect it through putty ti shows network connection error.
any help is appreciated
... (11 Replies)
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
LEARN ABOUT NETBSD
agr
AGR(4) BSD Kernel Interfaces Manual AGR(4)NAME
agr -- link aggregation pseudo network interface driver
SYNOPSIS
pseudo-device agr
DESCRIPTION
The agr driver provides link aggregation functionality (a.k.a. L2 trunking or bonding).
It supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol.
The agr driver supports the following link specific flags for ifconfig(8):
link0 Use the round-robin distribution algorithm. Don't use it unless you're really sure, because it violates the frame ordering rule.
-link0 Use the default distribution algorithm, which is based on the hash of DA/SA, TCI, and, if available, some upper layer protocol infor-
mation like ip(4) DA/SA.
link1 Disable LACP. Prevents any LACP or Marker messaging which leaves the ports in the default static configuration. Set this prior to
adding ports.
EXAMPLES
Create an agr interface, agr0, and attach re0 and re1 to it. In other words, aggregate re0 and re1 so that they can be used as a single
interface, agr0. The physical interfaces which are attached to the agr interface must not have any IP addresses, neither IPv4 nor IPv6.
ifconfig re0 inet xxx.xxx.xxx.xxx delete
ifconfig re0 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig re1 inet xxx.xxx.xxx.xxx delete
ifconfig re1 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig agr0 create
ifconfig agr0 agrport re0
ifconfig agr0 agrport re1
Destroy an interface created in the above example.
ifconfig agr0 -agrport re0
ifconfig agr0 -agrport re1
ifconfig agr0 destroy
SEE ALSO ifconfig(8)STANDARDS
IEEE 802.3ad Aggregation of Multiple Link Segments
HISTORY
The agr driver first appeared in NetBSD 4.0.
AUTHORS
The agr driver was written by YAMAMOTO Takashi.
BUGS
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation of the agr
driver always performs active-mode LACP and uses 0x8000 as system and port priorities.
The agr driver uses the MAC address of the first-added physical interface as the MAC address of the agr interface itself. Thus, removing the
physical interface and using it for another purpose can result in non-unique MAC addresses.
The current implementation of the agr driver doesn't prevent unsafe operations like some ioctls against underlying physical interfaces. Such
operations can result in unexpected behaviors, and are strongly discouraged.
There is no way to configure agr interfaces without attaching physical interfaces.
Physical interfaces being added to the agr interface shouldn't have any addresses except for link level address. Otherwise, the attempt will
fail with EBUSY. Note that it includes an automatically assigned IPv6 link-local address.
BSD February 23, 2010 BSD