Topic: Adding a second SME as server-only

[jeff]

Hi All, I added some new hardware and would like to (temporarily) use two SME servers on my network. The first one is up and running just fine ( in gateway and server mode ), but the second one ( in server-only mode ) is not accessible in any way, shape, or form.

At first I thought it may be the new nic I added to the server-only, as i've had lots of problems with linux and nics. But it's a RealTek chipset and I'm pretty confident that's not the problem ( modprobe looks correct, ifconfig eth0 seems correct ).

I added the IP address one up from the gateway IP, verified that it's not in the DHCP reserved range.

I don't think this should be an issue, but the server-only was actually changed via configuration from a server+gateway to server-only. It seemed to accept its new role without complaints.

Is there something I'm missing to tell the gateway-server that there's another server on the network? Has anyone else had any issues like this?

[Andy Bovett]

Hi Jeff

Not sure I can help too much, but I can tell you it's quite possible to have two SME servers on the same LAN - I've got two running right now. There are a few differences between my setup and yours by the sounds of it, but nothing that should stop it working as far as I can tell. Specifically:

1. I'm not using DHCP
2. Both are server only (no gateway)

Also, neither are being used as domain controllers (though one has that enabled - it's destined for a different network).

You say it's not accessible - can you ping it? Have you tried disconnecting the old server and talking to the new one in isolation? Maybe just connect one client PC to that server without the rest of your LAN (either use a separate hub or a crossover cable) and see if you can talk to it then.

I guess you may well have already tried some or all of these suggestions - sorry if they are all too obvious.

Andy Bovett

[Trevor B]

Jeff,

I'm running a second SME server just as a test server (in server-only with the other being the gateway etc.) just fine. It is using an old ne2000 ISA card (a little fun to set up, but works OK for what I want).

The gateway box is the dhcp/wins server and the PDC, whilst all these services are turned off on the test box (it is running a static IP outside of the assigned dhcp range). I have assigned the domain as a sub-domain of our domain (ie. test.mydomain.com) and it appears to work OK. Have also put this box in the hostnames of the domain (as test.mydomain.com). Can ping, ssh, browse etc. from within the local environment fine.

Only difference I can see is that I set mine up as Server Only from scratch.....

Any other info that can assist us??

Trevor B
jeff wrote:
>
> Hi All, I added some new hardware and would like to
> (temporarily) use two SME servers on my network. The first
> one is up and running just fine ( in gateway and server mode
> ), but the second one ( in server-only mode ) is not
> accessible in any way, shape, or form.
>
> At first I thought it may be the new nic I added to the
> server-only, as i've had lots of problems with linux and
> nics. But it's a RealTek chipset and I'm pretty confident
> that's not the problem ( modprobe looks correct, ifconfig
> eth0 seems correct ).
>
> I added the IP address one up from the gateway IP, verified
> that it's not in the DHCP reserved range.
>
> I don't think this should be an issue, but the server-only
> was actually changed via configuration from a server+gateway
> to server-only. It seemed to accept its new role without
> complaints.
>
> Is there something I'm missing to tell the gateway-server
> that there's another server on the network? Has anyone else
> had any issues like this?

[Kevin Tollison]

I have the same setup as Trevor with no problems.  The only thing i had to happen that caused any problems was I had to add it to the trusted networks in ZoneAlarm on my workstations

[jeff]

Thanks for all the responses. I have not had a chance yet to test out the stand alone server on its own. Based on your responses, I'm beginning to suspect that the mod for my nic is not correct. It looked correct according to the server, but I can't ping it or anything.

This weekend I'll try it out solo on the network, and then swap in a nic that I've used before with another SME server.
The vendor I purchased the nic from said specifically that it would work with Linux, it's a Realtek chipset, and the SME configuration recognized it as that automatically. So I figured I was in good shape. I'm running v5.6, does anyone know off hand whether there were significant changes to the 8139too mod or other mods for Realtek chipsets since v5.6?

Just wondering out loud, I'll check the changelogs this weekend.

Thanks again for the responses,

Jeff

[jeff]

Found the problem this weekend:

had the gateway server plugged into the switch uplink port. It worked with a single desktop on the network, but not when I added another machine.

Thanks for the help and comments, sorry but it ended up being a stupid user error...

[Andy Bovett]

jeff wrote:
 
> Found the problem this weekend:
>
> had the gateway server plugged into the switch uplink port.
> It worked with a single desktop on the network, but not when
> I added another machine.

Don't be too embarrassed! I spent several hours chasing a mystery network problem at a client's site before realising that that was what they had done!

If (as on many hubs and switches) the uplink connector shares a port with a regular connector, and both are connected, it simply acts like a crossover connector and links the two PCs directly without going through the hub - but of course then anything else plugged into the hub doesn't work correctly!

Andy