topic Re: ###Samba issue in Operating System - HP-UX

###Samba issue

Seven_1 — Tue, 22 Oct 2002 06:04:51 GMT

There's a system as below:
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

Re: ###Samba issue

U.SivaKumar_2 — Tue, 22 Oct 2002 06:12:03 GMT

Hi,

it is Drive letter conflict. Just map the samba share to some other Drive letter like X:
or Y: or Z:

regards,
U.SivaKumar

Re: ###Samba issue

Leif Halvarsson_2 — Tue, 22 Oct 2002 06:24:20 GMT

Hi

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.

Re: ###Samba issue

Seven_1 — Tue, 22 Oct 2002 23:39:53 GMT

Hello, LH and buddy:
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

Re: ###Samba issue

U.SivaKumar_2 — Wed, 23 Oct 2002 02:52:04 GMT

Hi,

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

Re: ###Samba issue

Leif Halvarsson_2 — Wed, 23 Oct 2002 07:26:55 GMT

HI
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.