Setting up new server for non internet network with PC.

[Richard Darling]

Laura,
First step maybe to eliminate the UNIX system, and get network connectibvity verfied.
I would also try to setup another PC on the same subnet(ex. ip - 192.168.1.9; 255.255.255.0) and plug it into the hub. Then try to communicate with this PC.

As mentioned earlier did you try to ping your loopback address on the PC and the UNIX box to verify that your cards are setup properly?

? ping 127.0.0.1

[Patrick Wallek]

Laura,

DO NOT use the 10-Base-T console port. That is probably most of your problem.

Connect to the 10/100 LAN port on the back of the box, which should be the only other RJ45 port on the box. The console port is for remote console connections ONLY, NOT normal LAN traffic.


Yes, you probably should have your PC IP address and name defined in /etc/hosts, but at the moment that is not your problem.

[Laura Rush]

I tried rebooting...then powering down the hub and reconnecting (green lights). This was with the lan wire plugged into the 10/100 LAN RJ45 port. Ping still does not work.

[Laura Rush]

I just noticed that one of my replies didn't post. Yes, I pinged the loopback on both the server and the laptop and both worked.

[Laura Rush]

off to try setting up another pc.

[Patrick Wallek]

OK, now that you've got the lan cable plugged into the 10/100 RJ45 port do this:

# lanadmin -x 0
and see what the status is. If it is showing AUTONEG, try doing:

# lanadmin -X 100FD 0

to hard set the speed at 100 Mbit Full Duplex. Then try pinging the PC and see what happens.

[Laura Rush]

ok, I ran the lanadmin command and installed a different computer and neiter worked.

[Laura Rush]

I also changed all my lan wires to different one's that I know work.

[Patrick Wallek]

Can you post the output of 'lanadmin -x 0' please.

[Sajith V Mannadiar]

Laura,

I would take the hub 'out of the equation' by connecting the PC and the unix server using a cross-cable.

[Laura Rush]

Driver is attempting to set the new speed Reset will take approximate 11 seconds and then it returned the # prompt.

[Laura Rush]

Saitjh,
I have had several people on this forum telling me not to do that with whats sounds to be good reason.
Laura

[Laura Rush]

lanadmin -x 0 is showing 100 Full-Duplex MANUAL

[Sajith V Mannadiar]

Laura,

Just out of interest.. what is the latest status on this? Were you able to connect?

[Laura Rush]

All,
Thanks so much for your help. Buying a new hub resolved the problem. I am able to ping and telnet to the two computers that I have added to my network. I still have one small problem. Yesterday, I added the route gateway of 192.168.1.0 and subnet mask to the etc/r.config.d/netconf and then was able to get a valid read out of the netconf file. I had a problem on reboot. I am doing an sh -x sbin/init.d/net start and getting an error that it failed to add route entry, because its interface is yet initialized. What does this mean if I am able to communicate with the server and seem not to have a problem?
Thanks again,
Laura

[Victor BERRIDGE]

I think the 0 at the end of your route isnt appreciated...
You should have as route something like 192.168.1.1
Dont fforget the metrics...
route add default 192.168.1.1 1

And check with netstat -r


All the best
Victor

[A. Clay Stephenson]

192.168.1.0 is what is referred to as the "network address"; with a subnet of 255.255.255.0 this means that the first usable address is 192.168.1.1 and the last usable address is 192.168.1.254. The .0 and .255 addresses for this subnet have special uses (eg broadcast to all the hosts on this subnet).

In short, you cannot use 192.168.1.0 as a host address and as mentioned you need to follow this with a metric of 1.