Topic: Network unreachable

[Chris]

Hello,
I have entered this same query in the general forum and no one could help.
I was wondering if anyone in here would be able to help.

I have checked, double checked and triple checked all of the settings and made sure that they are on the same domain name. but with no luck.

I even downloaded the full version of sme5.1.2 and checked the checksum. and then reinstalled that

Can two e-smith servers exsist on the same network?(i set the sme5.1.2 to server only)

This is starting to get stupid it just keeps saying "Connect: Network is unreachable" & "Connect: destination is unreachable" Logged on as root.


Hi all,

This is the second e-smith server on my network and i was trying out the sme5. the idea was to get sme5 up and running on server with more space & faster etc. then retire the old 4.1 e-smith box.
This was going well, it did its install bit and restarted asked me questions and the went to login. then i tried to get the manager on one of the hosts. thats where i am stuffed.
I carnt see it on the network and when you login to the new box as root and ping the loopback port (127.0.0.1) it works great. but if you try and ping anything else it says "Connect: Network is unreachable"

I thought that i must have done somthing wrong so i reinstalled the server, same problem.

I know the fist answer, test the network card, did that plugged it in and it works fine. checked and rechecked the settings all the ip addresses are valid and even tried to remove the gateway address etc but with no luck.

The card is a intel 82557 and it has the right driver installed 'eepro100'

This is not a complex network. 2 machines XP & 98 logging into the original e-smith box which is connected to a cable.

The server should be able to be seen on the network.

Any suggestions?

[Jon]

I have just done what your trying to do.
My first thought is:

Are they both set as DHCP servers?

I have a 4.1 running as file server and 5.1.2 as sever and gateway no problems.
The 4.1 will "retire" in about a week as it was the old server and gateway.

Jon

[Chris]

Thanks for you time jon,

But sadly no the 4.1.2 server is set to dhcp and the other is set to off. i also checked this when the machine starts up it says dhcp ( disabled )


Thanks,

Chris

[BYte]

Have you got them on the same Subnet?

[Chris]

I checked the subnets and they are both set to defaults 255.255.255.0 and ip addresses of 192.168.190.1 & 192.168.1.1.

Also last night i switched on the dhcp server of the 5.1.2 box and removed the other 4.1.2 server of the network (pulled its cable out of the switch) then tried to logon to the new server. no luck. I tried to restart everything in sight and then setup a user account and tried to jion the network. Again i got the 'connect: destination host unreachable" and "network unreachable."

I re installed the server accepting all defaults without the 4.1.2 server on the network and set it to server only with no internet access. but no luck.

Each time i have tried this i could ping the loopback port (127.0.0.1) and its own  adapters ip address (192.168.190.1) and get a reply.

And just to make sure i was not going mad i tested the utp cable iwas using on the laptop and it worked.

Any more ideas

Chris

[Jon]

Chris,
are you working through a hub/switch, if not is it a crossover cable?
Other than that I would try a diiferent ethernet card as it sounds like a faulty card or driver.
You could also try changing the slot the net card is in.
I've seen them work in one mother board and not in another.

HTH

Jon

[Julian]

Chris,
     I might be mistaken but I believe you said in your last e-mail that the subnet mask is 255.255.255.0 and the address are 192.168.190.1 & 192.168.1.1  If my IP schooling serves me well then your two machines are not in the same subnet try changing the subnet mask to 255.255.0.0 and see if it works better.

Julian Weber

[Kelvin]

Chris,

John is correct. You could also try changing the IP address of one of the servers to match the subnet of the other (ie. Server 1 = 192.168.1.1 and Server 2 = 192.168.1.2). Then you should be able to ping each other (and everything else for that matter).

Kelvin

[Julian]

Kelvin,
     I hope this doesn't come across the wrong way but my name is Julian not John

[Kelvin]

Quite Right Mate !

Sorry, must have been a little cockeyed when reading the screen !

Cheers !

Kelvin

[Chris]

Thank you guys,

Ok this is how i worked out that the subnet mask is 255.255.255.0

192.xxx.xxx.xxx - 223.xxx.xxx.xxx is a class C address therfore

n=network & H=host

class c should be NNN.NNN.NNN.HHH

But i didnt think about the fact that it is changing across subnets i will change the 5.1.2 server the current ip address of 192.168.1.X the server is on 1 and the dhcp range starts at 192.168.1.65 so i will give the new server an address of 192.168.1.10 that means its in the same range.

i see how that goes

[Chris]

Ok First of all, Thanks to the people that helped.

It turns out that it was the network card. I had two 8255X chipset cards by different companys and they both worked in the box at the same time under 2000 server. So i shear desperation i grabed the SMC 1211 network card that came with the cable connection and boom up it came. (its only a 10 base card i will have to get an 100 soon)

So it just goes to show you take nothing for granted when working with computers.

Chris