Sponsored Content
Full Discussion: Enable Remote desktop
Operating Systems AIX Enable Remote desktop Post 100355 by killer_boy on Monday 27th of February 2006 02:15:51 AM
Old 02-27-2006
Enable Remote desktop

hi every body here

i want enable RDP "Remote desktop Protocol" on aix application server

if some body help me i will be thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Remote control of cde desktop>?

Does anyone know if there is software out there top allow me to take remote control of a remote CDE desktop like using MS netmeeting? I do not mean mimick the window I mean take over/share the same session. Any help is appreciated (1 Reply)
Discussion started by: boat73
1 Replies

2. Solaris

How to enable solaris 9 to accept remote XDMCP

Hi, I want to enable solaris 9 to accept remote XDMCP connections. Please let me know what places i should look into and what configurations to be made. Thanks (1 Reply)
Discussion started by: 0ktalmagik
1 Replies

3. UNIX for Advanced & Expert Users

remote desktop

i want to access my group users desktop. can i did that by using xwd and xwud? else what can i do for that? (0 Replies)
Discussion started by: lakshmananindia
0 Replies

4. Red Hat

Problem in REMOTE DESKTOP INVOCATION

Hello sir, I am using VNC package for invoking the remote desktop to and from a FEDORA 8 machine and a WINDOWS XP machine. I have downloaded the VNC for both OSs and run it successfully. 1)When I invoked WINDOWS XP server, the I got it successfully as :-... (0 Replies)
Discussion started by: nsharath
0 Replies

5. SuSE

pocket pc remote desktop help?

pocket pc remote desktop help? login successful for display 10 started connecting rdpx11 channel is not present X11 RDP server started Screen depth is not 24 I try as solutions As the root user edit the file /etc/xrdp/sesman.ini and look for the section that looks similar to this:... (0 Replies)
Discussion started by: muratkaraca
0 Replies

6. Shell Programming and Scripting

Remote desktop

Hello, We are currently monitoring a server which sometimes does not allow people to login to it using RDP. Though the server is rechable we are not able to remotely login to it. Hence we monitor the connectivity by manualy connecting from our desktop through mstsc in windows. The... (1 Reply)
Discussion started by: venkidhadha
1 Replies

7. Ubuntu

remote desktop error (xrdp)

My friends, I installed ubuntu server 11.04 (x86_64) and activated remote desktop connection package which name is xrdp. I can connect successfully there is no problem. I have installed xrdp on ubuntu server 9.10 (x86) but I can't remote desktop. It gave an error messages. Picture is attached.... (4 Replies)
Discussion started by: getrue
4 Replies

8. HP-UX

Canīt get a remote desktop login through CDE

Hi all, I canīt get a remote desktop login through CDE only with root user. There are messages in the Xerror file: /usr/bin/X11/xset: bad font path element (#0), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font... (5 Replies)
Discussion started by: the0m3n
5 Replies

9. Shell Programming and Scripting

Triggering remote UNIX shell script from Remote desktop

I m trying to run a batch script in remote desktop which executes unix commands on the unix server...the problem is i wnt the output in HTML format.so in my batch script i m giving the cmd like ssh hostname path ksh HC_Report.ksh>out.html ...but it generates the HTML file in remote desktop .i... (2 Replies)
Discussion started by: navsan
2 Replies

10. Solaris

SUNOS 5.5.1 Remote Desktop

Hi All Is there a way to remote desktop to sun0s 5.5.1 system (unix) like vnc server for Windows? Thanks (2 Replies)
Discussion started by: Aloft
2 Replies
TNEF(1) 						      General Commands Manual							   TNEF(1)

NAME
tnef - decode Microsoft's Transport Neutral Encapsulation Format SYNOPSIS
tnef [options] [FILE] tnef {--help | --version} DESCRIPTION
This manual page documents the tnef filter. tnef decodes e-mail attachments encoded in Microsoft's Transport Neutral Encapsulation Format (hereafter, TNEF), which "wraps" Microsoft e-mail attachments. Unfortunately, these "wrapped" attachments are inaccessible to any e-mail client that does not understand TNEF. Fortunately, the tnef fil- ter can be used by any MIME-aware client to unpack these attachments. OPTIONS
-f FILE, --file=FILE use FILE as input ('-' denotes stdin). When this option is omitted, tnef reads data from stdin. -C DIR, --directory=DIR unpack file attachments into DIR. -x SIZE, --maxsize=SIZE limit maximum size of extracted archive (bytes) -t, --list list attached files, do not extract. -w, --interactive, --confirmation ask for confirmation for every action. --overwrite when extracting attachments, overwrite existing files. --number-backups when extracting attachments, if file FOO will be overwritten, create FOO.n instead. --use-paths honor file pathnames specified in the TNEF attachment. For security reasons, paths to attached files are ignored by default. --save-body FILE Save message body data found in the TNEF data. There can be up to three message bodies in the file, plain text, HTML encoded, and RTF encoded. Which are saved is specified by the --body-pref option. By default the message bodies are written to a file named message with an extension based upon the type (txt, html, rtf). --body-pref PREF Specifies which of the possibly three message body formats will be saved. PREF can be up to three characters long and each charac- ter must be one of 'r', 'h', or 't' specifying RTF, HTML or text. The order is the order that the data will be checked, the first type found will be saved. If PREF is the special value of 'all' then any and all message body data found will be saved. The default is 'rht'. --save-rtf FILE DEPRECATED. Equivalent to --save-body=FILE --body-pref=r -h, --help show usage message. -V, --version display version and copyright. -v, --verbose produce verbose output. --debug enable debug output. EXAMPLE
The following example demonstrates typical tnef usage with a popular Unix mail client called "mutt". Step 1 -- Configure ~/.mailcap Mutt can't use tnef for its intended purpose until an appropriate content type definition exists in ~/.mailcap . Here's a sample defini- tion: application/ms-tnef; tnef -w %s This mailcap entry says that whenever the MIME content type: application/ms-tnef is encountered, use this command to decode it: tnef -w %s The latter command string invokes tnef, specifying both the -w option and the attachment (created as a temporary file) as command line arguments. Step 2 -- Add The Filter To $PATH Mutt can't invoke tnef if the filter isn't accessible via $PATH. Step 3 -- Test Mutt Use mutt to read a message that includes a TNEF attachment. Mutt will note that an attachment of type "application/ms-tnef is unsup- ported". Press the "v" key to open mutt's "view attachment" menu. Move the cursor over the TNEF attachment and press the enter key to "view" the attachment. Mutt will launch tnef and invoke it using the command line syntax specified in ~/.mailcap (step 1). tnef then decodes all file(s) included in the TNEF attachment, prompting for confir- mation prior to creating an individual file (refer to -w option above). -w is useful here because it gives the end user a chance to view the filename(s) included in the mail message. Note that Mutt's attachment menu also supports a pipe option, which permits the user to pipe attachments to an external filter (how conve- nient). So, to list the contents of a TNEF attachment prior to decoding it, press the "|" key and enter this command: tnef -t SEE ALSO
metamail(1), mailcap(4), mutt(1), other email clients. AUTHOR
Mark Simpson. REPORTING BUGS
Report bugs to Mark Simpson <verdammelt@users.sourceforge.net> OTHER REFERENCES
This web page: http://support.microsoft.com/support/kb/articles/Q136/2/04.asp describes how to configure Microsoft email clients so that the TNEF format is disabled when sending messages to non-TNEF-compatible clients. Filter TNEF MIME Decoder TNEF(1)
All times are GMT -4. The time now is 12:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy