Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Vince on March 29, 2001, 03:08:10 PM

Title: Rebooted and Bam!
Post by: Vince on March 29, 2001, 03:08:10 PM

We installed and had E-Smith running for a couple of weeks with no major problems. I tried to reboot to prove how solid it all was and BAM! - no Internet access.

For grins I reconfigured with a different IP address and it too failed. So it must be a problem with the brand new networking cards (both 3com905B-TX), the hub has suddenly gone bad, the cable from the modem to the server has wigged out or I shouldn't have had that penguin sandwich for lunch.

This just seems really unusual to suddenly happen after a simple reboot when everything seemed to be working fine.

Any ideas?

Title: Re: Rebooted and Bam!
Post by: Vince on March 29, 2001, 04:29:16 PM

As an update to my problem, I swapped the cards in the configuration. I can now access the IP address, but the E-Smith-Manager times out waiting for a connection in my remote browser.

Since after the first reboot I've been able to see the E-Smith server via the Win NT network neighborhood - or is that because I input E-SMITH as the workgroup? Would the E-Smith-Manager not make contact if the local network card is bad?

Title: Re: Rebooted and Bam!
Post by: Mike Niedzwiedz on March 29, 2001, 07:31:18 PM

the e-smith work group should ideally be on the same workgroup as your other windows based pc's

If you can ping the local server address,   which by default is 192.168.1.1  i think, then just set "obtain ip address from dhcp server" you are on your way

you can also try setting your proxy to   'esmithaddress'  port 3128

cya