Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО08-27-2003 05:10 AM
тАО08-27-2003 05:10 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2003 06:01 AM
тАО08-27-2003 06:01 AM
Re: WINDBIND
# service winbind status
winbindd (pid 11952) is running...
if it is running, it should print a line that.
also, you can check the existence of the winbind deamon process:
# ps -aux | grep winbind
root 11952 0.0 0.3 4356 1812 ? S 16:02 0:00 winbindd
root 13286 0.0 0.1 3756 580 pts/9 R 16:04 0:00 grep winbind
the first line (with pid 11952) is the winbind process.
hth
Claudio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2003 06:14 AM
тАО08-27-2003 06:14 AM
Re: WINDBIND
This is what is returned:
#service winbind status
winbindd dead but subsys locked
Is there some configuring I need to do to get this running?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2003 06:27 AM
тАО08-27-2003 06:27 AM
Solutiontry restarting the service:
# service winbind start
This should be enough. Maybe deleting that file helps.
Ciao!
Claudio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2003 06:21 AM
тАО08-28-2003 06:21 AM
Re: WINDBIND
I think you should take a look at the log file.
You'll probably find it on the directory /var/log/samba with the name "log.winbindd". The log file usually says whats wrong.
I would bet on a bad or missing configuration on smb.conf.
Pedro.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2003 07:53 AM
тАО08-28-2003 07:53 AM
Re: WINDBIND
to check if winbind is functioning you should run the following commands:
1. getent passwd
this should return the domain user list in the format DOMAIN+Username
2. getent group
the same as 1 but this one eturn the Domain's group list
have fun
Avinoam