Topic: Server-only mode - no network

[john2]

I have been attempting to install SME server, but have been unable to achieve any type of network connectivity.  The hardware has run several versions of Linux (Ubuntu, Mandrake, Knoppix) in the past, so I believe it is compliant.  When I install SME server 7.0 in server-only mode, and set up the network to use my gateway at 192.168.0.1, I'm unable to ping the gateway.  I can do a console login as root or admin, view and use the text-based config, and ping localhost.  But there is no network connectivity in or out of the machine.  Turning DHCP on or off doesn't have any affect.

My gateway is a Coyote Linux box at 192.168.0.1 with no DHCP or DNS service, but I cannot ping this gateway from the SME server.  Meanwhile, I'm able to ping and utilize this gateway from other machines on the network.  Would appreciate your thoughts on how to debug this.

Thanks,

John

[william_syd]

Jonh2,

Here is a quick way to open your SME to the world and leave security just to your gateway/firewall.

Turn off dhcp server in your firewall/gateway.

Login to sme local console as admin.

Configure your sme as server-only, static ip of 192.168.0.10, enable dhcp server with a range of 192.168.0.20 - 192.168.0.30 and then activate the changes.

Access server-manager via the admin  console login. Go to Remote access.. Remote Management network 0.0.0.0 subnet mask 0.0.0.0 Secure Shell Settings... Allow public access (entire internet), yes, yes. then save.
Local networks..add network.. 0.0.0.0 0.0.0.0 192.168.0.1 and save.

Now try to access your sme.

If it don't work run ifconfig at a root login.

Code: [Select]

[root@tiger ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0B:6A:ED:B6:6B
          inet addr:192.168.2.9  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1005666 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1488157 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:298931400 (285.0 MiB)  TX bytes:1841633062 (1.7 GiB)
          Interrupt:185 Base address:0x6c00

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:62307 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62307 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7331429 (6.9 MiB)  TX bytes:7331429 (6.9 MiB)

vmnet1    Link encap:Ethernet  HWaddr 00:50:56:C0:00:01
          inet addr:172.16.8.1  Bcast:172.16.8.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vmnet8    Link encap:Ethernet  HWaddr 00:50:56:C0:00:08
          inet addr:172.16.223.1  Bcast:172.16.223.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@tiger ~]#

And see what it says for eth0

[john2]

William,

Thanks for your reply.  You enabled me to quickly eliminate the smeserver settings as the cause.

After lots of digging, it appears that the problem is with the Broadcom 4400 ethernet driver that is supplied with SMEserver 7.0.  I conclude this because:

  1) The networking is fine when I boot Knoppix and configure the network, and Knoppix identifies my network controller as Broadcom 4400.

  2) The networking does not work under SMEserver, and SMEserver also identifies my network controller as Broadcom 4400.

  3) SMEserver networking is also fine now that I've put a separate ethernet card into the system and directed SMEserver to use it.

I now have a working SMEserver, which was the goal.  However, it is a bit unexpected that my hardware (an Asus P4PE-RL with on-board LAN et al) which has worked under Mandrake, Ubuntu, and Knoppix does not currently work under SMEserver.  But that aside, I do appreciate your help and hope that the resolution to my issue will prove helpful to others.

Thanks again,

John

[fern]

john2

> it is a bit unexpected that my hardware (an Asus P4PE-RL with on-board
> LAN et al) which has worked under Mandrake, Ubuntu, and Knoppix does
> not currently work under SMEserver.  

The underlying OS is Centos4.3, so check compatibility with that.

Please report this to the bugtracker if you feel it should work and is not working.