Intermittent network connection problem
Jim Byrnes
jf_byrnes at comcast.net
Thu Dec 17 18:20:31 UTC 2009
NoOp wrote:
> On 12/17/2009 09:08 AM, Jim Byrnes wrote:
>> NoOp wrote:
> ...
>
>>> Another datapoint that I've found inherent on nearly all Win systems
>>> using Samba; if you click on "Entire Network" and then select the
>>> appropriate workgroup & system from there, it works in most cases. Give
>>> that a try as well.
>> Based on my experiences over the last couple of days I don't believe it
>> is an OS/2 problem. I don't have a lot of network expertise so I will
>> have to express this in layman's terms. Sometimes when Ubuntu boots it
>> does not initialize Samaba so there is nothing for other machines to
>> connect to. I believe this because if I use the Network file browser
>> when I cannot connect there is only a Windows network shown, but the
>> times I can connect there is a Samba and a Windows network displayed. If
>> I cannot connect the only solution I have found is to reboot Ubuntu
>> until I can connect.
>
> To check the status of samba:
>
> $ /etc/init.d/samba status
>
> Output should be:
> $ /etc/init.d/samba status
> * nmbd is running
> * smbd is running
>
> To start/stop/restart etc
> $ sudo /etc/init.d/samba {start|stop|reload|restart|force-reload|status}
>
> So if you find that samba is not running:
> $ /etc/init.d/samba status
> * could not access PID file for nmbd
> * could not access PID file for smbd
>
> you can restart:
> $ sudo /etc/init.d/samba start
>
> and then you should get the running status again:
> $ /etc/init.d/samba status
> * nmbd is running
> * smbd is running
NoOp,
Thanks alot for the detailed examples. They will save me a lot of
reboots.
Also, you helped me redefine the real problem and that is Samba not
starting. I just Googled that and see some hits, so maybe the longterm
solution lies there.
Thanks again, Jim
More information about the ubuntu-users
mailing list