On Tue, 2003-07-29 at 15:21, Richard Bown wrote: > Hi James > You were right something was using the port. > > > [EMAIL PROTECTED] log]# lsof -i :139 > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > vmware-sm 3554 root 5u IPv4 6966 TCP 172.16.27.1:netbios-ssn > (LISTEN) > > [EMAIL PROTECTED] log]# kill -9 3554 > [EMAIL PROTECTED] log]# lsof -i :139 > [EMAIL PROTECTED] log]# smbd -D & > [2] 7169 > [EMAIL PROTECTED] log]# ps ax > > 7125 ? S 0:00 pickup -l -t fifo -u -c > 7171 ? S 0:00 smbd -D > 7172 pts/0 R 0:00 ps ax > > So it looks like vmware is setup as a samba server as well as the host, > uhmm ! > > > Also this could be fun trying to get win98 on win4lin5 and winxp on > vmware working on the same machine :) > > with win4lin wanting the host to be server and vmware wanting to be a > server too. > Its a bit like Pandoras box, well at least there was hope at the bottom > of that box. > Looks like RTFM the vmware docs. > Has anyone on the list successfully run win4lin, vmware and samba at the > same time .? > > TIA > Richard
Best news is... you don't have to re-install of this. reading docs is a lot more productive than installing software. *grin* James > > On Tue, 2003-07-29 at 21:14, James Sparenberg wrote: > > On Tue, 2003-07-29 at 11:46, Richard Bown wrote: > > > Thanks James, > > > > > > log.smbd showed this:- > > > > > > [2003/07/29 19:32:47, 0] smbd/server.c:main(707) > > > smbd version 2.2.7a-security-rollup-fix started. > > > Copyright Andrew Tridgell and the Samba Team 1992-2002 > > > [2003/07/29 19:32:47, 0] smbd/server.c:main(751) > > > standard input is not a socket, assuming -D option > > > [2003/07/29 19:32:47, 0] lib/util_sock.c:open_socket_in(804) > > > bind failed on port 139 socket_addr = 0.0.0.0. > > > Error = Address already in use > > > > > > the other 2 log files I cant find, probably log.smbmount has'nt been > > > created yet. syslog is just showing the nmbd entry as poster earlier. > > > > > > > > > I've looked in all the other log files and cant see anything related to > > > smbd > > > > > > Not alot to yer teeth into > > > Richard > > > > No... not a lot.. but enough. Look at the last 3 lines. It can't start > > smbd because it is under the impression that something else is using > > that port. So it can't bind to it. As root do > > > > lsof -i :139 > > > > and see what it says This is the program/daemon that is blocking this > > port for you. If it isn't smb kill it if you can and try it again. > > .... I'm willing to bet (but not a large bet.) that smbd at some point > > has/had crashed and left behind it's socket marker. So an attempt to > > restart can't do it because as far as it's concerned... it's still > > running The other point I'm not so sure of is why the address is > > 0.0.0.0 This could be normal and I believe it is, but I'm not sure on > > this. > > > > James > > > > > > > > > > ______________________________________________________________________ > > > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://www.mandrakestore.com > > > > ______________________________________________________________________ > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
