From: Richard B. Gilbert on
Roland Titze wrote:
> On 10 Mai, 14:56, vedmak <vedma...(a)gmail.com> wrote:
>> Recently got ss20, installed solaris 7 and have no network
>> connection,

>>
>> any help is greatly appreciated
>
> It looks like your network configuration is broken.
> Check the files
>
> /etc/hostname.le0
> /etc/nodename
> /etc/inet/netmasks
>
> and change the line of file /etc/nsswitch.conf
>
> from:
> hosts: dns
>
> to
> hosts: files dns
>
> If you cannot find the reason for your network configuration problem
> then run "sys-unconfig" to re-configure your system completely.
>

Sys-unconfig should be used with caution! It wipes your existing
configuration and asks you to enter your whole configuration from
scratch! Man sys-unconfig should identify all the affected files and
maybe provide some hints.

Be sure that you have all the information needed BEFORE you start.

My own preference would be to find and fix the problem(s) instead of
throwing my toolbox at it.
From: Andrew Gabriel on
In article <56cf44ff-ea97-4906-b395-44714a5080b5(a)g21g2000yqk.googlegroups.com>,
Roland Titze <rtitze.news(a)googlemail.com> writes:
> On 10 Mai, 14:56, vedmak <vedma...(a)gmail.com> wrote:
>> Recently got ss20, installed solaris 7 and have no network
>> connection,
>> the interface tests fine from the bios,
>> but on boot I get
>>
>> Copyright (c) 1983-1999, Sun Microsystems, Inc.
>> configuring network interfaces:ifconfig: andromeda: bad address le0.

The reason for that is:

> and change the line of file /etc/nsswitch.conf
> from:
> hosts: dns
> to
> hosts: files dns

i.e. it can't lookup andromeda in the DNS before the ethernet is up.

>> le0: No carrier - cable disconnected or hub link test disabled?

My guess is it's using the AUI port (21 pin D-type), and you're trying
to use the RJ45. I can't remember how to switch ports off-hand, but it's
probably an OBP parameter.

--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]
From: Colin B. on
vedmak <vedmak90(a)gmail.com> wrote:
> Recently got ss20, installed solaris 7 and have no network
> connection,
> the interface tests fine from the bios,
> but on boot I get
>
> Copyright (c) 1983-1999, Sun Microsystems, Inc.
> configuring network interfaces:ifconfig: andromeda: bad address le0.
> le0: No carrier - cable disconnected or hub link test disabled?
>
>
> ss20 is hooked up to cisco 837, cable was tested, tried to change
> speed from auto full duplex to 10 full duplex, and 10 half duplex - no
> result.
>
> # ifconfig -a
> lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
> inet 127.0.0.1 netmask ff000000
> le0: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 0.0.0.0 netmask 0
> ether 8:0:20:fe:ed:33

(more...)

Well, you have a MAC address, and the interface is showing "running"
status, so you should be in business.

Even if the NIC is broken, you should be able to configure it, so the fact
that it's not configured suggests software. Carefully confirm the contents
of /etc/hostname.le0 and /etc/hosts. The former should either have an
address, or a hostname that resolves to an address in /etc/hosts. If these
are both in place and look good but still don't work, check for hidden
characters in the files!!!

Also, you can snoop the interface, even if it's not configured correctly.
This will at least show you if it's functioning, and also what network
space it's actually plugged in to.

Cheers,
Colin
From: vedmak on
On May 10, 8:00 am, Michael Laajanen <michael_laaja...(a)yahoo.com>
wrote:
> Hi,
>
>
>
> vedmak wrote:
> > Recently got ss20, installed solaris 7 and have no network
> > connection,
> > the interface tests fine from the bios,
> > but on boot I get
>
> > Copyright (c) 1983-1999, Sun Microsystems, Inc.
> > configuring network interfaces:ifconfig: andromeda: bad address le0.
> > le0: No carrier - cable disconnected or hub link test disabled?
>
> > ss20 is hooked up to cisco 837, cable was tested, tried to change
> > speed from auto full duplex to 10 full duplex, and 10 half duplex - no
> > result.
>
> > # ifconfig -a
> > lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
> >         inet 127.0.0.1 netmask ff000000
> > le0: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500
> >         inet 0.0.0.0 netmask 0
> >         ether 8:0:20:fe:ed:33
> > #
>
> > # ifconfig -a
> > lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
> >         inet 127.0.0.1 netmask ff000000
> > le0: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500
> >         inet 0.0.0.0 netmask 0
> >         ether 8:0:20:fe:ed:33
> > # cat /etc/defaultrouter
> > 192.168.1.254
> > # cat /etc/hosts
> > #
> > # Internet host table
> > #
> > 127.0.0.1       localhost
> > 192.168.1.211   andromeda       loghost
> > # cat /etc/resolv.conf
> > nameserver 68.94.156.1
> > nameserver 68.94.157.1
> > # cat /etc/nsswitch.conf
> > #
> > # /etc/nsswitch.files:
> > #
> > # An example file that could be copied over to /etc/nsswitch.conf; it
> > # does not use any naming service.
> > #
> > # "hosts:" and "services:" in this file are used only if the
> > # /etc/netconfig file has a "-" for nametoaddr_libs of "inet"
> > transports.
>
> > passwd:     files
> > group:      files
> > hosts:     dns
> > networks:   files
> > protocols:  files
> > rpc:        files
> > ethers:     files
> > netmasks:   files
> > bootparams: files
> > publickey:  files
> > # At present there isn't a 'files' backend for netgroup;  the system
> > will
> > #   figure it out pretty quickly, and won't use netgroups at all.
> > netgroup:   files
> > automount:  files
> > aliases:    files
> > services:   files
> > sendmailvars:   files
> > #
>
> > any help is greatly appreciated
>
> What if you do ifconfig le0 192.168.1.211 netmask 255.255.255.0 up ?
>
> /michael

tried that, the parameters for the network card will chage to the
specs above, yet nothing but loopback interface could be pinged. Not
even default router.
From: hume.spamfilter on
vedmak <vedmak90(a)gmail.com> wrote:
> tried that, the parameters for the network card will chage to the
> specs above, yet nothing but loopback interface could be pinged. Not
> even default router.

I suspect either your TP port is busted, or Andrew's suggestion is correct.
My SS20 is turned off behind me, but I think it was a matter of TPE
being enabled or disabled, and if the system thought there was no link on
the TPE it would fall back to AUI, though.

Could you post the output from "eeprom"?

And how hard would it be to obtain a "dumb" hub? The TPE port is a 10/hdx
port only, and I've heard of it having problems detecting link with some
newer switches (for very vague definitions of "new"...)

Another option is to obtain an AUI -> 10bT adapter, which might might need
to do anyway if the TPE port is dead.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/