Solaris Remote Desktop Login to Red Hat 5 Server

We have a number of Sun boxes running Solaris 8 and 9 and we need them to login to a Server running Red Hat 5. Have edited the /etc/hosts file to include the Red Hat hostname and ip address and when I enter the hostname it acts as if it is connecting to it, but then the cursor turns into a watch face and then kicks back to the login screen. Am I missing something minor or major??? Should also state that I can connect no problem to the server using hummingbird from PCs...

We are running SCOM 2012 server and have deployed the agent successfully to a number of Red Hat Linux servers. I am having an issue on about a quarter of the hosts, in that they appear as HEALTHY but are Grayed out and not green. When I look at the /var/opt/microsoft/scx/log/omiserver.log
file I see:
WARNING: wsman: authentication failed for user scom2012
I have verified that the system account is setup with the correct password and the runas account is setup with the correct password (i am able to deploy the agent from the SCOM server using it, so the passwords DO match).
Any ideas?
I've seen this on a few systems here when the agent has been upgraded but the old agent process does not die off. Just to rule it out, pick a node, make sure there are no instances of scxcimserver or scxcimprovagt and then start the agent and
see if the issue goes away. I've also seen wsman authentication failures related to the libssl issue that was fixed in yesterday's release.

Similar Messages

Remote Desktop cannot verify that this server belongs to the same server farm

Hello Team,
I am running Windows Server 2012 in my environment. I have 2 RDS Servers which are configured for load balancing. RDP to these hosts works just fine. But when i connect to any published remoteapplication , it gives me an error
Remote Desktop cannot verify that this server belongs to the same server farm.
What am i missing here, kindly suggest.
Binu Kumar Small Business Server Support

Hi Binu,
Do you have any progress?
If not, please make sure that the RD web access URL is configured as the farm name on each Remote Desktop Session Host server.
Here are some related threads below for you:
TS Web with TS Farm on W2K8 servers
https://social.technet.microsoft.com/Forums/windowsserver/en-US/09715e58-6e52-4c39-b445-4aa8fbc31cb0/ts-web-with-ts-farm-on-w2k8-servers?forum=winserverTS
RD Session broker issue; Cannot connect to one of the host servers through RDC
https://social.technet.microsoft.com/Forums/sharepoint/en-US/b9c15a01-a9cb-4793-8758-acd2e60ae7a5/rd-session-broker-issue-cannot-connect-to-one-of-the-host-servers-through-rdc?forum=winserverTS
RemoteApp - Cannot verify computers belong to the same server farm
https://social.technet.microsoft.com/forums/windowsserver/en-US/40be1eda-f752-4b64-bb47-dbe2156218f9/remoteapp-cannot-verify-computers-belong-to-the-same-server-farm
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Solaris remote desktop from Windows

Hi all i have windows xp and solaris 10 on the other machine...(home lan)
I want to make visual remote desktop connection to my solaris system...
do you know any effective tool for this?
thank you

Lion-OSeveral reasons where one of them being personal
taste ;-)
Next is versatility. Its pretty easy to setup an X
server, even in Windows these days, and as such you
hardly have to change anything on the Solaris part to
make this setup work. Which can be easier on your
part when it comes to patches and other updates.Thanks.
I had tried, not very hard, last week to setup X forwarding via SSH but couldn't find a free Windows X client to make it work. Cygwin is installed but perhaps I haven't fooled with it enough to find the way to make it happed. I'm sure my good buddy Google is knowledgeable on the subject once I know what questions to ask. ;)
My personal taste is for simple and secure and I'll likely follow your advice.
Thanks again!

Remote desktop connection to a windows server

Is it possible to connect to a Windows server on an iPad2 the way one can use Remote Desktop Connection on a Mac?

download and install any one of the RDC apps available on the app store.

TS2072 Remote Desktop Client for MS Windows Server 2003

I need to be able to access my work server to obtain information form our Windows 2003 Server. We have our product prices and other information on servers and today I use the remote desktop client that comes with Windows 7. I was hoping to find a suitable solution to allow me to use my macbook pro with OSX 10.7.4 Software. Does anyone know how to use OSX to make a remote desktop connection as you would through windows 7. I've seen CoRD and Microsoft did have a version but it's for older versions of OSX. I could run W7 but then I would have to purcase another copy and VM if I decided to run it virtual.
Thanks

This is not an Apple Remote Desktop issue - ARD is Apple's software for managing networked Macs - but CoRD and Microsoft Remote Desktop Connection for Mac should both work with Windows 2003 and both work on Mac OS X 10.7; I have used both on my systems. iTap Mobile RDP is another option, and the one I use daily since I've found it to be faster than either CoRD or Microsoft RDC, though iTap is not free.
Regards.

Remote Desktop Login events

I am trying to capture through SCOM events when specific accounts RDP into servers. I know it is logon type 3 but the workstation name the session is initiated from is blank. Is there a specific configuration required to log this information?
Thanks
Paul
Paul Glickenhaus

IP addresses or workstations are not captured when Remote Desktop are enabled without Network level Authentication.
Run sysdm.cpl to open system properties, select Remote -> Remote Desktop -> Allow Remote Desktop -> Allow connections only from computers running Remote desktop with Network Level Authentication.
Also you can use
this c# project to log authentication events in sql server

Remote desktop login

hello any one plz guide me ....i want to implement desktop to remote login like in windows ,
plz help..what are the API s i should refer
i think that i have to use rmi.....
but what about the screen.....? because when logged in another end desktop is shown in this side and he can access the files how to implement this?
thanking u in advance ..........

Read this and try again.
Good luck.

10.5.4 problem, Apple remote desktop - login window

Since the update to 10.5.4 I noticed two problems (probably not related):
1. in system.log, many lines about ARD
Jul 1 14:28:49 ekPB com.apple.launchd[376] (com.apple.RemoteDesktop.agent[1859]): Did not die after sending SIGKILL 2910 seconds ago...
etc. every 5 seconds
Finally ends with
Jul 1 14:30:08 ekPB ReportCrash[2050]: Formulating crash report for process ARDAgent[915]
Jul 1 14:30:09 ekPB com.apple.launchd[376] (com.apple.RemoteDesktop.agent[1859]): Exited abnormally: Bus error
Jul 1 14:30:09 ekPB com.apple.launchd[265] (com.apple.RemoteDesktop.agent[915]): Exited abnormally: Bus error
Jul 1 14:30:09 ekPB ARDAgent [2051]: ******ARDAgent Launched******
Jul 1 14:30:09 ekPB ReportCrash[2050]: Saved crashreport to /Library/Logs/CrashReporter/ARDAgent2008-07-01-143004ekPB.crash using uid: 0 gid: 0, euid: 0 egid: 0
Never had this before 10.5.4
ARD is of course activated...
2. The machine normally operating under my administrator account (and connected to a FireWire disk used by Time Machine), at two different moments, coming back, I find my machine showing the LOGIN window ...
in System.log:
Jul 1 11:16:12 ekPB loginwindow[407]: DEAD_PROCESS: 0 console
Jul 1 11:16:13 ekPB /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[1362]: Login Window Application Started
Jul 1 11:16:17 ekPB loginwindow[1362]: Login Window Started Security Agent
and
Jul 1 13:39:58 ekPB loginwindow[1362]: DEAD_PROCESS: 0 console
Jul 1 13:39:58 ekPB /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[1856]: Login Window Application Started
Jul 1 13:39:59 ekPB loginwindow[1856]: Login Window Started Security Agent
New login is normal and I don't find any reason to justify the end of the sessions of the connected user.
Any Ideas ? Thanks !
MacBook Pro core 2 Duo 2,33 GHZ 3 GB, 160 MB disk, Leopard 10.5.4 connected to ADSL by modem and Airport Extreme (last update 5.3.2 done)

Greetings...
Haven't found a similar thread yet, but if there is, my apologies. I have the same problem with the login, and I can't seem to fix it with a reboot. I have ran disk utilities as well as trying to get in through a remote computer. Any ideas/fixes besides reinstalling to 10.5.3 would be of a huge assistance.
~nathaniel

Solaris Remote Desktop Question...

Hello;
I have a quick ? for all you Solaris gods! :-)..
Is there a software package that will allow me to see a session of someone logged on!? For instance...
Windows Desktop, TeamViewer, etc., are packages that will interact with the currently logged on user & both people see the same thing, etc.
I have checked NXServer and VNC, and it doesn't seem that either of them do this, but rather use "individual" sessions so to speak!?
An I correct!? Or have I just setup the configuration files wrong!?
Thank you for the help in advance! This is important!

VNC can do this as long as both users are connected to the same session. VNC doesn't let you drop in on a session started outside of VNC.
I'm less familiar with NX, but I thought it was the same.
Darren

[Solved]Remote Desktop access to a Linux server?

Hi
I am connected to a Linux server through a VPN.
Usually I just run command-line apps via SSH.
Ther is one particular application that can only be started using a GUI applet on the server
but the server has no display.
Can I use my Mac's X server to see the graphical output and control that Linux Desktop?
What softwre do I need?
Regards
El

Found the answer on a previous thread
El

Remote desktop connections not showing in server manager 2012 for one of the session hosts

This is a three server deployment with one server being the connection broker, gateway, licensing, etc with two session host only servers.
rdmgr
rd1
rd2
Using the server manager on the rdmgr connection broker (or any other server for that matter) yields only connections from rd2 with nothing from rd1 displaying.
Users can connect to rd1 without issue.
At one point rd1 had the connection broker role installed also but high availability was not setup. I removed the role hoping it would correct the problem but no luck.
Any help would be appreciated. Thanks.

Hi,
1. Is rd1 part of a collection?
2. On rd1, in Computer Management, is the broker's computer account a member of the local RDS Management Servers group?
3. If you run the below command do you get a list of sessions:
query user /server:rd1
4. Any errors/warnings in either the broker's or rd1's event log?
Broker: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker
rd1: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker-Client
Both: System and other logs
-TP

Remote Desktop local printer redirection problem - Server 2012 Foundation

Hi,
I am trying to print from Windows Server 2012 Foundation to my local printer hosted on Windows 7.
When I enable local resources in the RDP client, I can see my printers on the server like redirected. All seems like no problem occured. But only print does not work. ;-)
I can see the document name in the queue with Error status.
I tried set up GP with disabling Easy print, the drivers are identical on both machines, event logs are clear.
The server is freshly installed, running only File server role. No Domain controller role is set. No Terminal Service is set (i think in Foundation is it not possible), only allowed RDP.
RDP client is the newest. I have not any problem to print from other servers (WS2003, WS2008R2) using this printer. Everytime is the printer automatically redirected to TS*** port and works.
I spent few hours searching solution with no effect.
Any idea? Many thanks!

Hi,
Did you find any error message during this issue?
Please check you have enabled necessary port for printer redirection on server side. You can check “Do not allow client print redirection” is disable under GPO setting. Also the user must have enough permission to print the document. Please check below link
for more information.
1. Terminal Server and Printer Redirection
2. Five reasons printer redirection causes Windows printing problems in RDS
Hope it helps!
Thanks,
Dharmesh

Using JSP & JDBC driver for SQL Server 2000 on Red Hat

I successfully have a .jsp app running on windows server 2000 using JDBC
driver for SQL Server 2000. Which I installed in order to the following
Red Hat:
http://msdn.microsoft.com/MSDN-FILES/027/001/779/install.htm
I moved the .jsp app over to the Red Hat 9 server running Tomcat, while
keeping the MS SQL 2000 on windows. The issue I have is setting up the
JDBC driver for SQL Server 2000 on the Red Hat server.
I created a folder called /usr/java/MSSQLdriver and unzipped the tar file with
the driver for SQL Server 2000. And ran the install.ksh script.
The /usr/java/MSSQLdriver/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
I chmod 0777 each of the *.jar files.
I then went into /etc/profile.d/tomcat.sh and adding the following:
CLASSPATH=.;/opt/msSQLjdbc/lib/msbase.jar;/opt/msSQLjdbc/lib/msutil.jar;/opt/msSQLjdbc/lib/mssqlserver.jar
Each time I login and pull up the termial I get the following error:
bash: /opt/msSQLjdbc/lib/msbase.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/msutil.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/mssqlserver.jar: cannot execute binary file
And can't connnect to the database within the .jsp app.
Is there anyone out there using DBC driver for SQL Server 2000 on the Red Hat server?
Michael

Sorry, I needed to correct some information of where the drivers were installed.
I created a folder called /usr/java/MSSQLdriver/new and untar the Microsoft file with the driver for SQL Server 2000. I ran the install.ksh script "sh install.ksh"
installed the driver into the default directory "/opt/msSQLjdbc".
The /opt/msSQLjdbc/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
Michael

Novell login not available with remote desktop on windows 7

Installed Novell Client 2 SP3 for Windows Server 2012 on my terminal server. When I log in from Windows XP to that terminal server I am getting an option to login with Novell Client. On Windows 7 however I only can logon to the server. What am I missing here?

djaquays <[email protected]> wrote:
> Mostly, that MS RDP for Mac ignores the authentication level:i:0 option
> in an RDP file and there's no GUI equivalent to force legacy
> authentication.
Microsoft's Network Level Authentication (NLA) feature is supported in
Windows Server 2008 and later terminal servers, and supported by
Remote Desktop Connection (MSTSC) 6.x and later terminal clients.
Windows XP did not ship with a MSTSC 6.x terminal client, but it is
available optionally through Windows Update.
The NLA authentication is essentially requiring that valid Windows
user account credentials for the Windows Server machine must be
provided /before/ the RDP-level terminal session connection is even
attempted or permitted. If the Windows user credentials you're logged
in with on the client workstation do not already satisfy this
requirement, the NLA-aware MSTSC clients will prompt you for valid NLA
credentials before even attempting to open the terminal session.
In other words, NLA doesn't directly have anything to do with whom you
will become authenticated as within the terminal session, or whether
you'll reconnect to some other already-running terminal session; it's
a new default mechanism which requires Windows credentials for
authorizing you to create an RDP connection to the Windows Server
machine "at all."
Unfortunately Windows Server 2008 and later don't permit you to turn
NLA completely off. You can configure the Windows Server to always
require NLA, which means pre-MSTSC 6.x terminal clients will be unable
to connect. Or you can configure the Windows Server to "not require
NLA" ("Allow connections from computers running any version or Remote
Desktop"), but this still means Windows Server will use NLA if the
workstation's MSTSC client supports NLA.
The only option which has been available to "disable NLA" even when a
Windows Server 2008 or later terminal server and a MSTSC 6.x or later
terminal client are involved is to configure the
"enablecredsspsupport:i:0" setting in the MSTSC client's .RDP file
(e.g. default.rdp in the My Documents folder), in addition to
configuring the terminal server to "not require NLA."
Once you have "Allow connections from computers running any version or
Remote Desktop" set on the Windows Server, and
"enablecredsspsupport:i:0" set in the MSTSC client, now you're back to
the Windows XP & Windows Server 2003 behavior where an RDP terminal
connection can be established without first having to supply NLA
credentials, and the first thing the MSTSC client user will experience
is the full normal credential provider-based login experience just
like you see at the physical console of the terminal server.
Note that if you do leave NLA enabled and supply NLA credentials
during the MSTSC connection attempt, after successfully using those
credentials to authorize creation of the RDP connection, the MSTSC
client will /also/ default to using the NLA credentials as default
credentials to attempt logging on with within the terminal session
itself. In other words, if you successfully supply NLA credentials,
by default you also become logged in on the terminal session and go
straight to the desktop of the Windows user account specified in the
NLA credentials. So even though "NLA credentials" and "whom I will
logon as within the terminal session" are two separate things, by
default the MSTSC client tries to use the same credentials for both.
But it's not that the NLA credentials "must" be used for logging in on
the terminal session; that's simply the default behavior. If you
leave NLA enabled on the Server 2008 or later terminal server, after
NLA credentials are successfully used to authorize creation of an RDP
connection, if you wanted to instead be prompted within the terminal
session with the normal credential provider login experience, enable
the "Always prompt for password" on the Windows Server 2008 or later
terminal server.
(On the Server 2008 or later machine, under "Administrative Tools"
find the "Remote Desktop Services" group and launch the "Remote
Desktop Session Host Configuration" console. Highlight/select the
"RDP-Tcp" connection, right-click and select "Properties". On the "Log
On Settings" tab elect "Always prompt for password".)
That sounds like probably the scenario which fits best for the "I have
a Macintosh-based client which doesn't allow enablecredsspsupport:i:0
/ authentication level:i:0." You would leave NLA enabled on the
Server 2012 machine, but enable "Always prompt for password" in the
RPC-Tcp connection properties on the Server 2012 machine. Such that
after NLA authentication was performed and Windows allowed creation of
the terminal session, instead of immediately also attempting to login
within the terminal session as the Windows account specified in the
NLA credentials, Windows will instead present the normal interactive
credential provider login experience to allow the user to specify whom
they want to login as.
Finally, note that everything described above applies even to a
Windows Server and Windows client workstation that do /not/ have the
Novell Client for Windows installed. The same mechanisms remain in
effect even once the Novell Client is installed; the presence of the
Novell Client just changes what credential providers would be used or
presented within the terminal session once the terminal session was
allowed to be created. The fact that NLA is required by default and
requires valid Windows credentials in order to authorize an RDP
connection is still the same, regardless of whether the Novell Client
is present or not.
Alan Adams
Novell Client CPR Group
[email protected]
Novell
Making IT Work As One
www.novell.com
Upgrade to OES Community
http://www.novell.com/communities/co.../upgradetooes/

The RPC server is unavailable while trying to take Remote Desktop of 2003 Server.

Dear All
Recently I am facing remote desktop login problem in on Windows 2003 Server.
While I am enter user name and password server give me logon error.
"The system cannot log you on due to the following error:
The RPC server is unavailable.
Please try again or consult your system administrator.
Kindly help me.........

I just started spontaneously having this problem yesterday. I am not aware of anything having changed that would prompt it, though I did do a Windows Update on all servers AFTER the problem manifested to see if that might fix it. (No such luck) For reasons
unexplained, the system HAS let me in a few times, though it hasn't been consistent, and now it seems to have locked me out entirely (except through the VSphere back door, explained below). I am running Windows 7 on my laptop, and I have received a report
of the same problem from another employee trying to log in from their computer, which I believe is also running Win7.
I am running two VMWare instances of Server 2003 R2, one Domain Controller and another production environment. I can RDP just fine to the DC, but not the production. Also, using the VSphere VMware management client on a separate machine, I CAN log in to
the production environment without a problem.
I have tried the fixes around restarting stopped services, but nothing has helped yet. I've also tried disabling my anti-virus temporarily, with no effect. I tried pinging the various IP addresses, and received timeouts on the 2 images, as well as their
host server. Again, though, I CAN log into the DC without issue.
Could someone please elaborate on how to create this registry key? On which image would I add this key? (I am a novice user, so using regedit is somewhat unfamiliar to me)
Any other thoughts about potential solutions?
Thanks!
Update Dec 15 2011: Just tried restarting the Production image, via VSphere, and then successfully logged in and out 3 times in quick succession by regular RDP. The symptoms have been temporarily soothed, though I wonder if the underlying problem remains?
Still no answer to why this happened in the first place, so I'd appreciate input.
Update Dec 16 2011: The problem came back this morning, and remained all day. I can still access by VSphere, but have other users who need to access by regular RDP. I'd rather not have to reboot the system constantly just to allow access... Any help is much
appreciated!

Solaris Remote Desktop Login to Red Hat 5 Server

Similar Messages

Maybe you are looking for