-----Original Message----- From: David Rysdam <[EMAIL PROTECTED]> To: Patrick Emonts <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thursday, June 17, 1999 2:44 AM Subject: Re: >Patrick Emonts wrote: >> >> Hello everyone, >> >> About a month ago I upgraded my SuSE 6.0 (2.0.36) to kernel 2.2.7 >> Yesterday I installed samba and ran into a big problem. Neither Win >> NT4 nor Win95 could see the linux box in their network. Ping & telnet >> worked fine. I changed delted the /etc/smb.conf file and replaced it >> with a very basic one (workgroup and home directories). Now both Win >> clients can connect to samba using "NET USE \\linuxbox\service" or >> search for it and find it, connect to remote drives, but the linux >> server does not show up in the network neighborhood. Suggestions are >> welcome :-) >> >> It basically works but it lacks ease of use. > >I believe the Linux box will have to announce itself to visible in >Network Neighborhood. Unfortunately I don't have a copy of Samba at >home, so I'm cc'ing myself at work to remind me to lookup my settings >(which work fine). I believe these are the applicable settings from my smb.conf remote announce = 192.168.1.255 #Obviously replace this with your network's ip address local master = yes os level = 255 # Ensures that samba wins all browser elections ; domain master = yes preferred master = yes Also check that on your Win 95 box that under Control Panel -> Network -> File and Printer sharing for Microsoft Networks Properties -> Advanced: Ensure that Browse Master is disabled and that LM Announce is No. This works fine on my LAN (Linux and 3 Win 98 boxes, not sure about NT). I think the problem might be that NT is winning the browser election and it doesn't have any LMHOSTS file set up for it. > >> A much bigger problem is the following. About 3 times a day (after 1 >> to 12 hours uptime) the linux box locks up for about 2 minutes and >> then the x server crashes. with a "BUS error". Today was particularly >> violent: Windowmaker crashed and reported a "signal 7: bus error". I >> went to the console to reboot and... nothing. no reboot. The screen >> said "System going down for reboot now..." and nothing happened. Same >> for the halt command. >> >> The system logs at the time of crash said the following: >> >> signal 7 (Bus error) >> INIT:PANIC: segmentation violation. giving up. >> >> Could someone please tell me what a signal 7 is? >> >> Thanks in advance. >> >> Patrick > >-- >My public encryption key is available from >www.az.com/~drysdam/crypt/rysdam.gpg.html >and of course www.keyserver.net >
