Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Terminal Services access to NFS Post 302197675 by wiggy332 on Wednesday 21st of May 2008 11:29:10 AM
Old 05-21-2008
Terminal Services access to NFS

Hi,

I am currently looking into a issue that has me scratching my head somewhat. Users from our branch down south use terminal services to work on within there windows desktop. The user used to be able to access NFS via her terminal services screen rather than reverting back to her windows desktop and entering via this route.

Our windows support guy is addament that this is a unix issue despite the issue only becoming apparent following an upgrade of terminal services. I have tried manipulating the users.map file in a few ways. I think the issue lays with the fact that her old windows log on and her old terminal services log on used to be the same. So when accessing NFs via terminal services previously the user map file was picking up the user name and granting her access. Her TS log on is now appended with a 2 so for example if it were me with the issue the windows log on would be:

cwiggle
and the TS log on - 2cwiggle

Now obviously these do not match with in the users.map file on NFS, i have tried having 2 entries for her with the 2 different log ons, i have also tried having the user with one entry but both the windows and TS usernames next to each other. Has anyone ever come across this issue before/know a work around? I am really just after a 2nd opinion as to whether this is a unix support issue and im being silly or if it is vice versa and i am right in stating that this is probably a TS setting somewhere? The only remaining thing i can think of trying is to get the terminal services name changed to the same as her windows log on again if possible?

Any advice much appreciated.
Thanks
 

7 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

Terminal Services profiles

Hi guys i'm new in windows 2000 server so please bear with me. My quiestion is how can you remove all the icons and even the start menu using terminal services. I have a windows xp machine that is part of a domain i installed terminal services. I can login no problem but i want to be able to... (2 Replies)
Discussion started by: josramon
2 Replies

2. Windows & DOS: Issues & Discussions

ws2003 terminal services.

New to ws2003 standard edition. I configured this server to be a domain controler, terminal services server and the cal server as well. I added users and joined them to the remote desktop users group. Still cant log in as a configured user. I get the erro message that this user needs to join the... (1 Reply)
Discussion started by: fruiz
1 Replies

3. UNIX for Advanced & Expert Users

NFS services

What are all the services/daemons we use in NFS configuration? I know that nfs,portmap,nfslock the the services we use.But I am not sure that which service wil do what job? Is there any other services running for NFS? What services are running on server side and what services are running in... (4 Replies)
Discussion started by: praveen_b744
4 Replies

4. Windows & DOS: Issues & Discussions

nfs/nis - microsoft services for UNIX adminstration

hello, I am using "microsoft services for UNIX adminstration" as an nfs/nis client in order to connect to a remote NFS folder with NIS authentication nfs mount seems to fail on the authentication stage. I get the login box from the client, but any (NIS mapped) loging seems to reject me.... (2 Replies)
Discussion started by: ynoatan99
2 Replies

5. IP Networking

can't access with FTP using terminal

hi, I was wondering why I can't connect through Terminal to my FTP server. It perfectly works through client FTP (I've attached an image with settings) http://dl.getdropbox.com/u/72686/cushy2.png But I can't using the terminal I tried many times the same password I use on FTP... (4 Replies)
Discussion started by: aneuryzma
4 Replies

6. Red Hat

NFS Access Issue

Hi, I am facing issue on NFS. I have shared /data file file system on Server 192.192.192.1, added below lines in /etc/exports /data 192.192.192.2(rw,no_root_squash,sync) the owner of /data directory was test(uid 500) and same I have mounted on another server 192.192.192.2 where the... (3 Replies)
Discussion started by: manoj.solaris
3 Replies

7. Red Hat

Winbind and pam - restrict all services except for samba access

Hi, I have recently taken control of a number of RHEL5.3 servers that have samba shares setup on them and are authenticating using pam and winbind. My issue is that any user that has an active directory account can currently log in to the linux boxes using their ad credentials. I need to... (0 Replies)
Discussion started by: klyne
0 Replies
telnetd(8)						      System Manager's Manual							telnetd(8)

NAME
telnetd - The DARPA telnet protocol server SYNOPSIS
telnetd [-debug [port]] [-D modifier ...] FLAGS
Starts telnetd manually, rather than through inetd, on alternate TCP port number port (if specified). Prints out debugging information. modifiers are: Prints information about negotiation of telnet options Same as options with additional processing information Displays the data stream received by telnetd Displays data written to the pty Not yet implemented DESCRIPTION
The telnetd daemon is a server that supports the DARPA (Defense Advanced Research Projects Agency) standard telnet virtual terminal proto- col. telnetd is invoked by the Internet server (see inetd(8)) normally for requests to connect to the telnet port as indicated by the /etc/services file (see services(4)). The -debug flag may be used, to start up telnetd manually. If started up this way, port may be specified to run telnetd on an alternate TCP port number. The -D options may be used for debugging purposes. This allows telnetd to print out debugging information to the connection, allowing the user to see what telnetd is doing. The telnetd daemon operates by allocating a pseudoterminal device (see pty(7)) for a client, then creating a login process that has the slave side of the pseudoterminal as stdin, stdout, and stderr. telnetd manipulates the master side of the pseudo-terminal, implementing the telnet protocol and passing characters between the remote client and the login process. When a telnet session is started up, telnetd sends telnet options to the client side, indicating a willingness to do remote echo of charac- ters, to suppress go ahead, to do remote flow control, and to receive terminal type information, terminal speed information, and window size information from the remote client. If the remote client is willing, the remote terminal type is propagated in the environment of the created login process. The pseudoterminal allocated to the client is configured to operate in cooked mode, and with XTABS and CRMOD enabled (see tty(7)). The telnetd daemon is willing to do: echo, binary, suppress go ahead, and timing mark. telnetd is willing to have the remote client do: line mode, binary, terminal type, terminal speed, window size, toggle flow control, environment, X display location, and suppress go ahead. The telnetd daemon never sends telnet go ahead commands. Note that binary mode has no common interpretation except between similar operating systems (Unix compatible systems in this case). Note also that the terminal type name received from the remote client is converted to lowercase. The telnet command uses the default Type-of-Service value recommended by RFC1060, which is as follows: Low delay You can configure this value by specifying it in the /etc/iptos file. For more information, see iptos(4). By default, the telnetd daemon starts the login dialog using the login string specified in the message field of the /etc/gettydefs file. If you want to use a customized banner, create an /etc/issue.net or /etc/issue file. The telnetd daemon reads the file that exists and writes its contents over a new telnet connection prior to starting the login dialog. If both files exist, only the /etc/issue.net file is used. CAUTIONS
Some telnet commands are only partially implemented. Because of bugs in the original 4.2BSD telnet(1), telnetd performs some dubious protocol exchanges to try to discover if the remote client is, in fact, a 4.2BSD telnet(1). FILES
Specifies the command path. Specifies the path name for the network issue identification file. Specifies the path name for the issue identification file. RELATED INFORMATION
Commands: telnet(1). Files: iptos(4), issue(4), issue.net(4). delim off telnetd(8)
All times are GMT -4. The time now is 02:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy