Very Computer

We just upgraded various machines to Solaris 2.6 and have had a
problem crop up.

Basically, when a machine with no DNS entry tries to connect via TCP
to any of the Sol2.6 machines one of two things happen:

1. Takes a LONG time to connect if it's on the local network
(xxx.yyy.zzz.0)
2. Doesn't connect at all if it's not on the local network

Any machine that has a DNS entry has no problems connecting to the
machines. This problem is affecting everything that uses TCP (pop3,
http, telnet, ftp, etc.)

I've administered Solaris and other unices and have not come up
against anything like this except perhaps on FreeBSD where it would
not let you log on if you didn't have an appropriate reverse-lookup.

Has anyone else had this problem with Solaris 2.6? If so, how did you
clear it up, work around?

thanks much.. !
fid..

Add a reverse lookup for the machine, or fudge one into the machine's
/etc/hosts file.

: 2. Doesn't connect at all if it's not on the local network

I'd say there's another cause for this one.  Make sure the machines can
ping each other, if not, check the routing/default gateways.

--
Brandon Hume    - hume -> bofh.halifax.ns.ca, http://www.bofh.halifax.ns.ca/
                - Finger for Geek codes, PGP, /dev/zero, yadda yadda.

Quote:>: 2. Doesn't connect at all if it's not on the local network

>I'd say there's another cause for this one.  Make sure the machines can
>ping each other, if not, check the routing/default gateways.

For those on the internal network, when going from server to server,
there was no problem connecting since they either had the other host's
name and IP address in the /etc/hosts file or was available via DNS.
When going to a workstation w/o an entry in the /etc/hosts file nor an
entry in DNS.. THAT's when a problem occurred.

Am I missing something here? Did I miss something when installing 2.6?

btw, this happens on ALL the installs of 2.6. :/

fid..

We just upgraded various machines to Solaris 2.6 and have had a
problem crop up.

Basically, when a machine with no DNS entry tries to connect via TCP
to any of the Sol2.6 machines one of two things happen:

1. Takes a LONG time to connect if it's on the local network
(xxx.yyy.zzz.0)
2. Doesn't connect at all if it's not on the local network

Any machine that has a DNS entry has no problems connecting to the
machines. This problem is affecting everything that uses TCP (pop3,
http, telnet, ftp, etc.)

I've administered Solaris and other unices and have not come up
against anything like this except perhaps on FreeBSD where it would
not let you log on if you didn't have an appropriate reverse-lookup.

Has anyone else had this problem with Solaris 2.6? If so, how did you
clear it up, work around?

thanks much.. !
fid..