HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Samba error
Operating System - HP-UX
1838627
Members
3293
Online
110128
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2002 04:31 PM
01-29-2002 04:31 PM
Samba error
Morning, all.
I successfully compile and install samba2.2.2 on HP10.20, and could start ./nmbd -D without error.But when I use ./smbd -D,I got following error:
[2002/01/29 18:12:50, 0 lib/util_sock.c:open_socket_in(830)
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already in use
Could you tell me what's the meaning of this sentence, and how to solve this.
By the way, the samba was on a NT lan,with a primary NT DNS server,this HP10.20 only be configured as cache DNS.
Thanks
--Frank
I successfully compile and install samba2.2.2 on HP10.20, and could start ./nmbd -D without error.But when I use ./smbd -D,I got following error:
[2002/01/29 18:12:50, 0 lib/util_sock.c:open_socket_in(830)
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already in use
Could you tell me what's the meaning of this sentence, and how to solve this.
By the way, the samba was on a NT lan,with a primary NT DNS server,this HP10.20 only be configured as cache DNS.
Thanks
--Frank
DAEMON
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2002 04:53 PM
01-29-2002 04:53 PM
Re: Samba error
If might be that netbios is running already on your system. Check it ..
# ps -ef|grep netbios
If this is the case this will cause NMBD not being able to bind to that port.
You can edit /etc/rc.config.d/lmu and put "0" at the line that says
LMU_NETBIOS
Then reboot your system so that netbios doesn't start. Now start nmbd again.
# ps -ef|grep netbios
If this is the case this will cause NMBD not being able to bind to that port.
You can edit /etc/rc.config.d/lmu and put "0" at the line that says
LMU_NETBIOS
Then reboot your system so that netbios doesn't start. Now start nmbd again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2002 12:35 AM
01-30-2002 12:35 AM
Re: Samba error
You can also check /etc/services if another service uses port 139.
Hardy
Hardy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2002 02:05 AM
01-30-2002 02:05 AM
Re: Samba error
Just a quickie, if samba started or shutdown abnormally, it's possible that the port is left in a FIN_WAIT state. You could try netstat -an and see if the port has any connections / up. If it has, they should time out, or you can use ndd (11.) or nettune to configure the timout manually.
Hope this is of some use!
-ChaZ-
Hope this is of some use!
-ChaZ-
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP