[Samba] Win2K3 Server, in Terminal Session,

[MJBarber at Hearst.com]

I have almost the same setup (NT4 domain, with W2K3 Terminal Server)....

I am using Suse 9.2, Samba 3.0.21b, with winbindd on a generic x86 server.
No special package configurations...just the rpms from samba for Suse.

I do have the same problems.
 -- I have home directories mapped for users.  When I log into the Term
Server with RDP my home directory on my Samba box comes up just fine..

What permissions do your users have on the Term Server?  I am an
administrator on the box, but all my users see their home directory as
well.  Can you do mapping when logged directly into the machine?  What do
the samba logs say?  Is the samba server forcefully rejecting the
connection?

Good luck,
MJB




-----Original Message-----
From: samba-bounces+mjbarber=hearst.com at lists.samba.org
[mailto:samba-bounces+mjbarber=hearst.com at lists.samba.org] On Behalf Of
michele-lists at pupazzo.org
Sent: Tuesday, February 28, 2006 11:16 AM
To: samba at lists.samba.org
Cc: helan at ce.chalmers.se
Subject: Re: [Samba] Win2K3 Server, in Terminal Session,

* Peter Helander (helan at ce.chalmers.se) wrote:
> Hello Steven
> 
> I read about your problem I am sorry I can't help you.
> 
> Because have the same problem. And have looked everywhere to
> 
> find a solution so I wonder if you have fixed it
> 
>  
> 
> Best regards
> 
>  
> 
> /Peter

Somewhat late, but I think this might be related:
http://support.microsoft.com/?kbid=818528

"""
Problems when more than one user accesses the same file through Terminal
Services """

See if it helps,
Michele


> 
>  
> 
> I have looked for several days and can not find the answer to my 
> problem, but I'm sure it has to be a simple issue. I'm trying to map 
> drives inside Windows Server 2003 Terminal Session from a local Samba 
> server but can't get connected.
> I figure the problem is in Windows Registry but can't find web page on 
> what needs to be changed to get this working.
>  
> I built a new Windows 2003 server. Logon to the new server through 
> Terminal Services (Remote Desktop Connection). Once connected I open 
> Windows Explorer and try to browse over to my SAMBA server. My problem 
> is that I get a Windows Error box saying I "\\FOO_SAMBA is not 
> accessible." Then goes on saying I might not have permission. The last 
> line says "The request is not supported."
>  
> Tried mapping a known share from the FOO_SAMBA server 
> (\\FOO_SAMBA\test) and I get a different windows error message saying 
> "The drive could not be mapped because no network was found."
>  
> The domain this server is in is an is older NT4 style domain. (Not 
> Active
> Directory.) The Windows 2003 Server is a member of the ADOMAIN Domain. 
>  
> The FOO_SAMBA server in running on Solaris 8 sparc server. I do NOT 
> have any domain machine names configured in /etc/passwd file. Only 
> users I want to allow to connect are in the /etc/passwd file and also 
> part of the 'adomain' group in /etc/group file.
>  
> I do not have any problem connecting to the FOO_SAMBA server from 
> Win2K or WinXP workstations. Can even connect to shares from other 
> Win2k Terminal Server, inside a Remote Desktop Session.
>  
> 
>  
> 
>  
> 
>  
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba