I am having a problem getting samba to work with terminal server. My
smb.conf file looks like:
[global]
workgroup = TOTALFLOOD
server string = Samba Server
security = SERVER
encrypt passwords = Yes
password server = atlantic
username map = /etc/samba/smbusers
log file = /var/log/samba/%m.log
max log size = 0
dns proxy = No
printing = lprng
...etc
which works fine with workstations. However, whenever logging onto
terminal server with a domain account, I cannot get samba to give the
user access. The server just keeps asking for a name and password but
will not accept any combination. A local account on the terminal
server works fine if the username and password are the same as for the
domain account.
I tried using a sniffer to determine what the difference is but, swelp
me, I cannot see it. Any ideas how to fix this?
I am using samba v2.2.1a on Redhat 7.0.
--
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
stephen@totalflood.com
change security to domain
and add machine account into domain
add samba into domain
-----Original Message-----
From: Stephen Carville [mailto:stephen@totalflood.com]
Sent: Friday, November 30, 2001 7:24 AM
To: Samba List
Subject: Terminal Server and Samba
I am having a problem getting samba to work with terminal server. My
smb.conf file looks like:
[global]
workgroup = TOTALFLOOD
server string = Samba Server
security = SERVER
encrypt passwords = Yes
password server = atlantic
username map = /etc/samba/smbusers
log file = /var/log/samba/%m.log
max log size = 0
dns proxy = No
printing = lprng
...etc
which works fine with workstations. However, whenever logging onto
terminal server with a domain account, I cannot get samba to give the
user access. The server just keeps asking for a name and password but
will not accept any combination. A local account on the terminal
server works fine if the username and password are the same as for the
domain account.
I tried using a sniffer to determine what the difference is but, swelp
me, I cannot see it. Any ideas how to fix this?
I am using samba v2.2.1a on Redhat 7.0.
--
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
stephen@totalflood.com
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
A workaround for this is to put an entry in your crontab file to restart the Samba server. Ken Rory D. Hudson wrote:>Hello there everybody, > > > >I have been doing some reading about Samba and terminal server, I am >currently running in a Citrix Terminal Server environment with Windows >Service Pack 4. It looks like it is a known issue that for whatever >reason the Samba server will not allow connections at a certain time. I >have been given workarounds in the past (i.e. create several different >hostnames for the same ip address), but there still reaches a critical >mass on my server (about 40 users). The server is hardly sweating, but >this is causing major problems with my users. I was hoping that perhaps >in some newer versions of Samba this problem might have been addressed. >Has it? Please let me know, any information regarding this would be >great. > > > >Rory > > >
Hello there everybody, I have been doing some reading about Samba and terminal server, I am currently running in a Citrix Terminal Server environment with Windows Service Pack 4. It looks like it is a known issue that for whatever reason the Samba server will not allow connections at a certain time. I have been given workarounds in the past (i.e. create several different hostnames for the same ip address), but there still reaches a critical mass on my server (about 40 users). The server is hardly sweating, but this is causing major problems with my users. I was hoping that perhaps in some newer versions of Samba this problem might have been addressed. Has it? Please let me know, any information regarding this would be great. Rory