Perfect!!! lsof -i :139 solved the problem, it was one
of the services started with vmware, I just installed
vmware on my system and was causing this trouble. When
I stopped it everything came back to normal.
Thanks a lot, your help was very precise and
fast.
Roberto
--- "J. Craig Woods" <[EMAIL PROTECTED]> wrote:
> Roberto Armenteros wrote:
> > True what you said. I checked
> /var/log/samba/smbd.log
> > and I found the problem. For some reason I get the
> > error: bind failed on port 139 socket_addr =
> 0.0.0.0.I
> > am not running any service on that port. I then
> tried
> > running smbd with the -p otion and specified any
> > particula port "in my case 140", and it started
> the
> > daemon successfuly, but then I couldnt access the
> > shares from another computer. What do you think I
> > should do next?
> >
>
> Hmmmm, now that sounds strange. Port 139 should be
> dedicated to
> netbios-ssn. Hopefully you don't have another
> service binding to it,
> such as a trojan (highly unlikely). So what is using
> it? Try running a
> "lsof -i :139" and you can do a "netstat -a | grep
> LISTEN". See what you
> come up with. Take another look at smb.conf.
> Something could have got
> screwed up in there....
>
> Dr John
>
>
> > Want to buy your Pack or Services from
MandrakeSoft?
>
> Go to http://www.mandrakestore.com
>
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
