My 300mhz o2 has suddenly stopped being able to get on the web. It was able to get on any network I hooked it up to. Never seemed to have to mess with it.

The 400mhz o2, on the other hand, has to always be setup to look for the specific IP that I hook up to. Any time I move it to a new network I have to run proclaim and do the whole setup networking... check the hosts file,.. etc etc. Then it hooks up.

But, the 300 mhz stopped being able to get online suddenly this last week and I have no idea why.

When I run proclaim it says it can't access ec0 device.

But yet when it boots it doesn't complain about the ec0 or the IP.

There is this message now about "can't login to ...... /directory/ posted in pic/ .... and gives a libsec code.In image.

also something about netscape server...

Any thoughts?

Attachments

Last edited by Intuition on Sat Nov 18, 2017 8:56 am, edited 1 time in total.

Your choice, but I'm a fan of chkconfig off as many of the old built in services I don't use, so there's always that options. But don't let that get in the way of a good excuse to learn some new diagnostic skills...

I am wondering why it is 192.168.1.255 instead of the .192.168.1.1 OR even 109. I had success with 1 through 9 before as the last digit. Like, I am trying to figure out why I see the 255 in the gateway list. Also.. what does.. "link#1" mean?

This morning on regular boot it says it couldn't configure the ec0. usually it doesn't error out there but this time it did. Maybe the hardware is just bad?

I could buy one of those $15 network cards on ebay. I have successfully setup my 400mhz o2 at three different places just by running proclaim and then making sure the entries are in the /etc/hosts file. The 300mhz used to just connect to anything... I could plug in a cat 5 and it'd work no matter what... now it's being a princess.