Re: TNS-12518: TNS:listener could not hand off client connection.

Sybrand Bakker <sybrandb_at_hccnet.nl> wrote in message news:<eml3e0p1h6kskidq125fo2rtqs515adtso_at_4ax.com>...
> On Tue, 29 Jun 2004 16:14:08 GMT, Mladen Gogala <gogala_at_sbcglobal.net>
> wrote:
>
> >On Tue, 29 Jun 2004 08:12:53 -0700, David Jakubowski wrote:
> >
> >> ntus2err: sd=113, op=14, resnt[0]=507, resnt[1]=0, resnt[2]=0
> >> nsbequeath: error reading REDIR/NSE msg
> >> nserror: nsres: id=101, op=72, ns=12560, ns2=0; nt[0]=0, nt[1]=0,
> >> nt[2]=0; ora[0
> >
> >You are having REDIR/NSE messages, which means that you're hitting
> >a router of some kind. Do normal network connections like telnet,
> >ssh, scp,ftp, or X11 work normally? Protocol error usually signifies
> >either library mismatch or a network problem.
>
>
> I'm not sure whether you are right. The bequeath protocol after all IS
> non-routable.

in linux, you can set the range of ports to be used in /etc/sysctl use sysctl -a to view the settings.

sorry, I'm still relatively solaris illiterate, and my Solaris ref manuals are on the bookshelf at work.

why not try reducing the range of ports to say 1024::49000 and give it a go again? you may be bumping into NAT, ip_masq or some other pothole up in the high port range, perhaps a trojan ? (on solaris, yeah, right)

Pd Received on Wed Jun 30 2004 - 00:22:47 CDT