- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ###Samba issue
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
Forums
Discussions
Discussions
Discussions
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
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
10-21-2002 11:04 PM
10-21-2002 11:04 PM
###Samba issue
server: 1 L2000 , HP-UX11.0 , samba 2.2.3a
client: about 45 PC(win2K)
Every PC mapped L2000's certain directory as driver named T:\ .
There'a a application and DLL files saved at T:\tst. My trbouble
is that the application can't run stable, it will be closed
automatic. I found a red cross appeared at T:\ driver icon, and when
I double click the icon, windows told me :
???An error occurred while reconnecting T: to \\10.194.21.16\tst
Microsoft Windows Network: The local device name is already in
use. This connection has not been restored.???
So, I confused :
1. Is there a quntity limitied about smaba's clients?
2. If it is, how can I extend?
3. Is the problem bringed by server or client?
4. Which configuration should I check again?
TKs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 11:12 PM
10-21-2002 11:12 PM
Re: ###Samba issue
it is Drive letter conflict. Just map the samba share to some other Drive letter like X:
or Y: or Z:
regards,
U.SivaKumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 11:24 PM
10-21-2002 11:24 PM
Re: ###Samba issue
Is it enough memory on the Samba server, In the installation manual you can find recommendations.
Is NIS running on the Samba server, I have had some problems with my Samba server related to NIS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2002 04:39 PM
10-22-2002 04:39 PM
Re: ###Samba issue
The server has 4 G physical memory,and when I run # top ,
1382324K free. So, I think I have enough memory .
And I didn't use NIS.How about the related issue with your
NIS, would you suggest me what I should check?
BRS
seven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2002 07:52 PM
10-22-2002 07:52 PM
Re: ###Samba issue
I bet this problem has nothing to do with server side.
This error is displayed when there is Drive letter conflict ( when the specified drive letter is occupied already ) in windows 2000
Just try changing the Drive letter.
regards,
U.SivaKumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2002 12:26 AM
10-23-2002 12:26 AM
Re: ###Samba issue
I agree vith U.SivaKumar, this is most likley to be a drive conflict.
My problem with NIS was that I used NIS for user authentication in Unix and the NIS server was unstable. When the NIS server was down the Samba server was unavilable from Windows clients too. But the error messages was different from yours.