HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Upgrading from Samba 2.x to 3.x , for Clients usin...
Operating System - HP-UX
1834015
Members
2741
Online
110063
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
03-22-2006 06:55 PM
03-22-2006 06:55 PM
Upgrading from Samba 2.x to 3.x , for Clients using Kerberos %m is not working
Hi,
we upgraded an old Serviceguard-Cluster providing SMB-Shares to a new hardware.
Along with the hardware there was an Upgrade of the complete System from HPUX 11.00 to 11.11 and Samba 2.2.8 to 3.0.14a (HP A.02.02).
We are using the following share-definiton:
[backup_nb]
comment = Share using Netbios-Name of Client
path = /cifs/data/backup/%m
This provided every Client with his own directory (named by the netbiosname)
I was told the reason for that, but I have no idea how to make a workaround.
Clients using Kerberos connect to samba over port 445 where no netbios wrapper listens, so the %m macro cannot reolve the netbiosname.
As a consequence every client tries to connect to his directory identified by the client-IP-Adress.
As a first shot I created tons of symbolic links for all IP-Addr to the Netbios/Hostnames.
But here I see a pitfall, if a client would change either his IP-Addr. and not his hostname and vice versa.
I cannot just replace all %m with %I for the IP-Adress of the client, because we have several applications relying on the hostname.
Another issue is, that generation of logfiles lead to logfilenames containing the IP-Addres in the filename instead of the hostname.
Did somebody else hit this problem ?
How was it solved ?
Any Ideas are very welcome.
Thanks Christian
we upgraded an old Serviceguard-Cluster providing SMB-Shares to a new hardware.
Along with the hardware there was an Upgrade of the complete System from HPUX 11.00 to 11.11 and Samba 2.2.8 to 3.0.14a (HP A.02.02).
We are using the following share-definiton:
[backup_nb]
comment = Share using Netbios-Name of Client
path = /cifs/data/backup/%m
This provided every Client with his own directory (named by the netbiosname)
I was told the reason for that, but I have no idea how to make a workaround.
Clients using Kerberos connect to samba over port 445 where no netbios wrapper listens, so the %m macro cannot reolve the netbiosname.
As a consequence every client tries to connect to his directory identified by the client-IP-Adress.
As a first shot I created tons of symbolic links for all IP-Addr to the Netbios/Hostnames.
But here I see a pitfall, if a client would change either his IP-Addr. and not his hostname and vice versa.
I cannot just replace all %m with %I for the IP-Adress of the client, because we have several applications relying on the hostname.
Another issue is, that generation of logfiles lead to logfilenames containing the IP-Addres in the filename instead of the hostname.
Did somebody else hit this problem ?
How was it solved ?
Any Ideas are very welcome.
Thanks Christian
never touch a running system
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