| 12 | | FWIW, sometimes, NMBD runs for days. Other times, it stops after seconds. I usually start the SAMBA server in the startup folder. That always shows as successful, and it usually works for a while. Then, other machines cannot "see" this one in the client. Sometimes, just loading the *.EVF file (on the client) will make it connect. More often it won't connect, as if NMBD was not running (it is). Just as often, NMBD has quit running, for no apparent reason (although it seems that the logs show that there is no IP address, which would seem to be impossible). No other program has these problems. It is only the SAMBA client |
| | 12 | FWIW, sometimes, NMBD runs for days. Other times, it stops after seconds. I usually start the SAMBA server in the startup folder. That always shows as successful, and it usually works for a while. Then, other machines cannot "see" this one in the client. Sometimes, just loading the *.EVF file (on the client) will make it connect. More often it won't connect, as if NMBD was not running (it is). Just as often, NMBD has quit running, for no apparent reason (although it seems that the logs show that there is no IP address, which would seem to be impossible). No other program has these problems. It is only the SAMBA client, and NMBD.EXE. |
