I have an old Sol 8 box and I cannot telnet into it nor connect to the internet.

I am logging in as root.

I have SBC Yahoo DSL using a 2wire DSL router.

What I have done:
/etc/hosts:192.168.x.xx bobafett loghost bobafett
/etc/hostname.le0:bobafett
/etc/nodename:bobafett
/etc/netmasks:192.168.x.xx 255.255.255.0
/etc/resolv.conf: domain sbcglobal.net
/etc/resolv.conf: nameserver 68.94.xxx.x
/etc/resolv.conf: nameserver 68.94.xxx.x (these are not duplicates)
Swtiched the lan cables between the windows box (this one) and the solaris box: same.
I am getting a link light on the back of the solaris box and at the router.

I was getting this during startup:
"no carrier - cable disconnected or hub test link disable?"
So I did:
bash-2.03#eeprom 'tpe-link-test?=false'
which stopped the msg of course but was not a fix.

When I login to the router admin page from one of my Windows boxes, I can see both Windows boxes and the Solaris box on Home network summary. The solaris box shows as 'bobafett' and as inactive. All three boxes had the same firewall settings. I manually changed the FW settings for bobafett to ensure it allowed ftp, telnet, nnmp, blah blah blah but I still cannot telnet into it, use ftp, or get out to the internet.

bash-2.03# ping bobafett
bobafett is alive

bash-2.03# route -n get 192.168.x.xx
route to: 192.168.x.xx
destination: 192.168.x.xx
mask: 255.255.255.0
interface: le0
flags: <UP,DONE>
recvpipe,sendpipe,ssthresh,rtt,msec,rttvar,hopcount,mtu,expire
0 0 0 0 0 0 8232 0

Ps -ef | grep net returns nothing.

Telnet and ftp are both enabled in /etc/inetd.conf.

Any thoughts? I am fairly new to unix.

Thanks

Never... give... up!

Addendum to my previous post.

From /etc/inetd.conf:
ftp stream tcp6 nowait root /usr/sbin/in.ftpd in.ftpd
telnet stream tcp6 nowait root /usr/sbin/in.telnetd in.telnetd

Never... give... up!

Might paw through this. I haven't use solaris 8 on a sparc so I can't say for sure.

http://docs.sun.com/app/docs/doc/80...

Pretty sure that there was a config app but you can do it file by file. Solaris 10 still has all those files.

Might see this too.

http://www.tech-recipes.com/solaris...

I read it wrong and answer it wrong too. So get off my case you peanut.

Thanks for the links jefro. I will check them out this evening.

Update:
I ran sys-unconfig and manually re-entered the network info. I verified the name service info from my carrier.

Each time I updated the name service, there was a problem using NIS+, NIS, or DNS. I also verified the DNS info with my carrier.

The only error I can remember is from using NIS, which stated in part:"ybind could not communicate to yserver. Please run ybinit -c after login".

Never... give... up!