Topic: e-smith server not seen by network

[brad wright]

Hi all,
after installing e-smith 4.1.2 on a server prev. running 4.1.1 (faultlessly) i am unable to 'see' the e-smith server in the network neighbourhood of any client machine (win 95/98). User account  has been set up (same login/passwprd as 4.1.1 account) and windows workgroup name has been changed and match the setting on the e-smith box (workgroup name is 'WORKGROUP').
The network connection is fine...I can still recieve email and web pages on the client machines, just no e-smith server in the network neighbourhood.

Hope someone can help.

Thanks in advance,
Brad

[Dan Brown]

I had the same problem; it was caused by samba not starting.  _That_ was caused by the fact that somehow the upgrade process renamed /etc/samba/smb.conf to /etc/samba/smb.conf.rpmsave.  Fixing this was pretty easy:

# cd /etc/samba
# mv smb.conf.rpmsave smb.conf

[brad wright]

Thanks for the response... i didnt think of that, however i just checked and the smb.conf is correctly named.
I fixed the problem last night with the help of a friend, it turned out that none of the client machines had file sharing installed (once that was corrected, everything worked). The weeird thing is, it WAS working fine under 4.1.1 and i definatly didnt uninstall nor did i change any of the related settings on the client machines when i installed 4.1.2 over the top of the old 4.1.1 on the server.

So even tho its working fine now...i'm very curious to know why it worked fine under 4.1.1 then required file sharing to be installed on the client machines under 4.1.2.

Any ideas??? .......anyone.......???


thanks,
brad

[Tom Carroll]

I accidently up my /etc/samba/smb.conf file on my SME 5.1.2 machine (I think).

I inadvertedly used /sbin/e-smith/expand-template /etc/samba/smb.conf instead of /etc/smb.conf

I canot see my server from my windows client now.

I checked the contents of the /etc/samba/smb.conf file and it is empty except the default Mitel header as found in all config files.

Is this what caused my server to drop of the network?  If so, how do I fix it?

If not, then what might it be?

Thanks!

Tom