This isn't really the place for S10 questions (and you've not mentioned
that OpenSolaris is involved), but a little googling and some source
code provides the answer:
"bad port" is reported by in.rshd under the following circumstances:
bad_port = (port >= IPPORT_RESERVED ||
port < (uint_t)(IPPORT_RESERVED/2));
[
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/cmd-inet/usr.sbin/in.rshd.c#522
]
IPPORT_RESERVED is defined as 1024, so any port which is >1024 or <512
will generate this message.
I've not checked whether this port range is part of the RFC, but you may
need to check what port(s) the client is connecting from. The same code
existed all the way back to at least Solaris 7, so I doubt this is a new
issue :-)
What is the client program? Maybe the relevant binary has had it's
setuid bit (or appropriate privileges) stripped? (I'm guessing here...).
If both V490's are Solaris 10, then any further issues should be through
your normal Sun Support channel.
Regards,
Brian
Krishnan wrote:
Hi,
I am having some problems with rsh/remsh on solaris 10
while trying to rsh from a V890 to another V890 , I am getting this error message
sometimes "rcmd: socket: Cannot assign requested address" and the
/var/adm/messages file shows this
May 26 11:26:54 hostname rsh[7895]: [ID 521673 daemon.notice] connection from
"hostname" (IP address) - bad port
This is causing an issue because the app team is cont.injecting files from/to
servers
the release level is Solaris 10 5/08 and the patch level is Generic_127127-11
Any help would be appreciated
--
Brian Ruthven Sun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG
_______________________________________________
opensolaris-discuss mailing list
[email protected]
