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]
Making IT Work As One
Upgrade to OES Community

Similar Messages

  • Ipad bluetooth keyboard not working with remote desktop

    My clients ipad bluetooth keyboard works any other time, just not when connected to his servers via the remote desktop. PC Windows 7 Servers.
    I'm trying to get the keyboard information, but any ideas?

    Are you using an app like LogMeIn Ignition to access your servers? I believe that LogMeIn Ignition requires you to tap a little keyboard button near the bottom of the screen to activate use of the keyboard (that's how it works in Splashtop Remote, can't be much different in LogMeIn Ignition.)
    Are you sure the app you have supports blue tooth keyboard support with remote desktop? (not sure if they have to, I just recall seeing this in Splashtop patch notes awhile ago.)

  • Hardware accelerated views have been disabled because they are not compatible with remote desktop

    Just started getting this error after updating to CC and latest NVIDIA drivers:
    I don't run Remote Desktop. After this message appears, the checkbox in my preferences is disabled:
    If I reboot my computer, the checkbox is again enabled, but then the error message about the remote Desktop appears, not right away, but after several minutes.
    Windows 7 Pro
    Intel i7 CPU X980 @ 3.3GHz
    24GB RAM
    GeForce GTX 680, Driver 320.49
    AE CC
    Thanks for any help.

    Currently running apps:
    Adobe Prelude
    So, as a test, I did the following:
    Launched Adobe After Effects CC.
    Looked at "Preferences" -> "Display" -> "Hardware Accelerate Composition......" ... it is enabled
    Locked my workstation. [Windows key - L]  I don't have a screensaver ... just plain black.
    Typed my password to unlock.  The dialog box shown at the top of this thread appears. 
    Closed AE.
    Re-launched AE.
    The option in Preferences is unchecked, but it is selectable.
    So, that is MUCH more convenient thatn having to reboot the machine.  Don't get me wrong here ... it's still annoying.  It's especially annoying because I developed the (good) habit of locking my workstation whenever I walk away from it.  During a typical work day, I may lock/unlock my workstation ten times ... or more.

  • Struggling with Remote Desktop to Windows 8.1 Guest OS running Win 8.1 Pro Hyper-V

    Host:  Windows 8.1 Professional with Hyper-V
    Guest: Windows 8.1 
    Host is running wifi
    Created a internal network that is bridged to WIFI.
    Host can connect to internet.
    Guest can connect to internet.
    Cannot RDP from host to guest.
    - Guest allow remote management is turned on
    - Tried with firewalls turned off
    - ping from host to guest works
    - ping from guest to host works
    What can I do?

    The message is a generic one
    Remote Desktop can't connect to the remote computer for one of these reasons:
    1) Remote access to the server is not enabled
    2) The remote computer is turned off
    3) THe remote computer is not available on the network
    Make sure the remote computer is turned on and connected to the network, and that remote access is enabled
    Just to note:
    - I did enable remote access in guest (but maybe it did not work)
    - remote computer (guest) was turned on (VM was running)
    - remote computer could be pinged. Perhaps there were other problems in routing traffic into the guest

  • Sun Ray 1 with remote desktop on windows 7 ultimate

    I have a windows 7 ultimate box. I have an unopened Sun Ray 1. Before I open the box, I want to know if I can use the Sun Ray 1 to connect to my windows 7 ultimate box. If I can, how do I do it? Is it easy?

    No. Sun Rays are truly thin, meaning there is no OS or clients installed on the device. You need a server to use it.

  • Easy print not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1

    Easy print is not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1 . Printers dont get redirected when you connect to the terminal server. The server we are connecting to has Windows 2008 server.  On 32 bit Windows
    7 and windows XP clients Easy print is working fine and printers get redirected in terminal server.

    I am having the exact same problem. Windows 7 works fine, but 8.1 will not redirect printers. Others said to check local policy terminal services settings and my setting are all set as they should.
    I think Windows 8.1 is not telling the terminal server what printers it has.

  • Does OS mountain lion come with Remote desktop?

    My 2012 Pro does not have remote desktop anywhere on it.  All the other macs I've encountered have had it preloaded.  Is mountain lion just the first os to not have it installed?

    Remote Desktop is not included with Mountain Lion nor is it preloaded on new Macs. You have to buy it:
    Many features that were previously only available on Remote Desktop, screen sharing for instance, are now part of OS X though.

  • HP Laserjet 1020 not working through remote desktop

    I have a hp laserjet 1020 that I am vpn and remote desktop to a computer at work. I am suupose to be able to print from remote desktop to my local printer (the hp laserjet 1020) using the microsoft terminal Easy Print. The printer is showing up in the printer list, but when I try to print I get an error of Printer not ready.  The printer is working fine on the local machine, just not through the remote desktop. I have install the printer drivers on the machine that I am remoting into , just to make sure. Is there anything else I can try. I am not finding any firewalls on either end blocking it?

    After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others.  This problem as far as I have come across deals exclusively with HP printers.  In simple terms:  the drivers are flawed.  This 1022 is a prime example.  It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder.  Enter a remote desktop session and ALL of them populate except the 1022.  This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers.  All except the 1022. 
      Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver.  I used a 1200 PCL driver.  Now log back into your RDT server and hockus pocus! there is your printer.  Totally un-usable because the driver will not run this printer.  Caveat:  each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
    Moving on we go to the HP OfficeJet/LajerJet2840.  Same thing.  It won't pass through as remote printer in RDT.  Go local.  Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
    While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
    Hey HP?  Whats with the drivers??
    Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing.  You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.

  • How to set a default printer using vbs on windows 2008 R2 with remote desktop services

    It seems I wasn't in the right places before / threads. BIG Sorry.
    Here's the problem: I have this VBScript:
    On any computer, the Default Printer "HisBadPrinter"
    strPrinterName = "mySuperPrinter"
    Set objPrinter = Helper.CreateObject("WScript.Network")
    objPrinter.SetDefaultPrinter strPrinterName
    In Xp, Windows 7 it work perfect, The default printer is being changed.
    But in Remote Desktop on Windows Server 2008 R2 it is not working, with any type of account (Administrator, user, powerUser...) "HisBadPrinter" is always the default printer and it's always printing on it without any error messages.
    Help Please.

    Ok, here what I have in my ControlPanel > Devices and Printers
    Adobe PDF (redirected 3)
    Brother HL-4150CDN series on infovm1dc (redirected 3)
    Generic / Text Only (redirected 3)
    HP Color LaserJet 3800 PCL 5c on infodc3 (redirected 3)
    Microsoft XPS Document Writer
    Microsoft XPS Document Writer (redirected 3)
    PDFCreator (redirected 3)
    Now Here what I got when I executed the bit of code :
    Adobe PDF (redirected 3)
    Microsoft XPS Document Writer (redirected 3)
    Generic / Text Only (redirected 3)
    Brother HL-4150CDN series on infovm1dc (redirected 3)
    HP Color LaserJet 3800 PCL 5c on infodc3 (redirected 3)
    PDFCreator (redirected 3)
    DIRECT - Brother HL-2460 (redirected 2)
    PDFCreator (redirected 2)
    Fax (redirected 2)
    Microsoft XPS Document Writer (redirected 2)
    Brother HL-2460 on infodc3 (redirected 2)
    Microsoft Office Document Image Writer (redirected 2)
    Brother HL-4150CDN series on infovm1dc (redirected 2)
    Microsoft XPS Document Writer
    There is no printer called "\\ALPHA\HP LaserJet P2015 Series PCL 6".

  • Mouse not captured in remote desktop session

    I have one (but only one)  Hyper-V VM which has the "mouse not captured in remote desktop session" issue. I have researched this problem extensively and so far none of the suggested fixes I have found are working.
    The VM is running Windows Server 2012. It is completely up-to-date.
    The Hyper-V server its running on is running Windows Server 2012 R2. Also up-to-date.
    All integration services are offered in the VM according to the Hyper-V management tool. I have tried removing all integration services from the VM and putting them back with the Hyper-V management tool. This had no effect.
    I have also set the VM to "Detect HAL" using BCDEdit... this had no effect.
    The only suggestion I could not try is the suggestion to use the "Insert Integration Services Setup Disk..." command from the "Action" menu. I can not do this because a message to "Tap to choose what happens with this device"
    message pops up when I try it... and, guess what? I can't "tap" it because like everyone else we don't use touch screens in the server room. I can't click it either because my mouse doesn't work. Trying to click it just brings up the same "mouse
    not captured in remote desktop session" message I am trying to get rid of.
    Any suggestions?

    During your description, it seems you are using the touch screen to operate the server, personal experience is in general we don’t choose the touch screen to do this, please
    try to use the general mouse try again, it seems your device not compatible with the Server 2012R2. You can search your device in Windows Server Catalog to identify the hardware compatibility.
    The Windows Server Catalog.
    Hope this helps.
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows 2012 + hyper-v + mouse not captured in remote desktop session + integrated services installed

    windows 2012 + hyper-v + mouse not captured in remote desktop session + integrated services installed

    I am using Server 2012 R2 with Hyper-V and CentOS 6.5 that installed GNOME.
    Same no mouse on remote desktop session or on the host's Hyper management interface.
    From my knowledge, CentOS from 6.4 build in include the IS, how do I update the IS in CentOS 6.4-6.5 guest OS? Any detail docunment for reference?
    Thank you.

  • Stuck with Remote Desktop 3 without the serial number:(

    I am the new tech assistant for my lab of 35 macs..
    The computer used for managing the lab with remote desktop has crashed.
    I have found an older model mac with remote desktop. I'd like to transfer that application
    to my newer mac...but It will ask me for the serial number of which I do not have.
    The old tech assistant has gone..and along with it...the software and document.
    I have turned this lab upside down and I've found the box Apple Remote Desktop 3
    but nothing else. I thought maybe the serial number would be on it.  But I see
    only the bar code... I am frustrated to no end. They don't answer my emails for help
    Love using Apple Remote Desktop 3 user but can not anymore:(

    IIRC the serial number was never on the outside of the box so have you looked inside the box? Do you see the booklet that came with the box? Is the Serial Number inside? The Serial Number takes this form:
    Who is not answering your emails for help?
    Having read the terms and conditions of this forum prior to posting you'll know these are user-to-user forums and Apple are not listening, so it's difficult to see what any of us here can do to help? Perhaps if you find the purchase receipt you might be able to contact your local Apple Rep and ask if they have a record of it?
    You can still use Remote Desktop by purchasing it again from the App Store. It costs far, far less than the installer media version and does not require a serial number. All you need is an Apple ID and an associated debit or credit card.

  • Troubleshooting error with Remote Desktop 3.1

    Have OSX Server 10.4.10 on a powerPC with Remote Desktop 2.2, Security scans advise to update to Remote Desktop Client 3.1. Everytime I do this I get this error "The Remote Desktop Administrator software failed to start du to an unexpected error. The Remote Desktop software may not be installed correctly or the computer may require a restart."
    I have two machines on this network that are giving this error, one this server and the other a laptop. Version 2.2 was running and working just fine prior to the update, now its broke. Is there a log file somewhere to try to figure this error out? Has anyone else experienced this issue? I have already tried to reset permissions, and reboot, but nothing works.

    Just to confirm my understanding, you are running the ARD 2.2 Administrator on the server, and something is advising you to upgrade that system to the ARD 3.1 client? If that's the situation, then do not upgrade. The 3.x client will not work with the ARD 2.2 administrator. If you did indeed upgrade, you'll need remove ARD using the instructions here and then reinstall ARD 2.2 from your installation disks.
    Similarly, if you've upgraded any client workstation to the 3.x client, you'll need to remove it and reinstall the 2.2 client using this installer. It says it's an "updater", but it will work anyway.
    Hope this helps.

  • Hardware acceleration has been disabled because it is in compatible with remote desktop

    So I go and lock my pc only to come and find that after effects says hardware acceleration has been disabled because it's incompatible with remote desktop
    I have looked around and others have said to delete a certain preference file but they did not give the file location
    Does anyone know where this pref file is?

    And what is the question? C'mon, the files and folders are properly labeled. Don't make it any more complicated...

  • Centro will not sync with Palm desktop - Calendar and/or Contacts

    I have used a Palm device for many years. Acquired a new Centro. Upon installation of Palm Desktop (on Windows XP) that came with Centro, all contacts, calendar, to do, memos, etc transferred to the Centro during installation. 
    Subsequent changes to contacts and/or calendar on Centro are not syncing with Palm desktop when Hot Sync is performed. Hot Sync starts and appears to complete normally. To Do list and memos appear to sync just fine. Have tried changing conduits to have Centro overwrite desktop. Have uninstalled/reinstalled Desktop many times.
    Hot Sync log:
    HotSync operation started for Daniel M. Key on 07/02/08 13:35:13
    OK Quick Install
    OK VersaMail
    OK Memos
    OK Media
    OK Tasks
    -- Backing up MultiMail BData to C:\Palm\MD\Backup\MultiMail_BData.PDB
    -- Backing up PmTraceDatabase to C:\Palm\MD\Backup\PmTraceDatabase.PDB
    -- Backing up HxSyncRegistry to C:\Palm\MD\Backup\HxSyncRegistry.PDB
    -- Backing up Saved Preferences to C:\Palm\MD\Backup\Saved_Preferences.PRC
    OK Backup
    HotSync operation completed on 07/02/08 13:35:19
    Please help. Thx.
    Post relates to: Centro (Sprint)

    I have a Centro/Verizon Wireless using Versamail with accounts established for personal POP and Exchange e-mail synchronization.  The latter account is for work.  Previously I owned a Treo 650p using Versamail. 
    When I first installed Palm OS Desktop and synched to my Centro device, it was on a Windows XP home computer, and no Versamail accounts were defined.  First I downloaded and installed the Versamail version which allowed Exchange synchronization.  I exported the Treo650p contacts list to a disk file, and imported it onto the Windows XP home computer into the Palm OS Desktop installed with the Centro-supplied CD.  This synched the imported contacts list to the Centro fine.  After I defined all the POP and Exchange accounts, synchronization with the office Exchange contacts list worked fine, and still does.  Synchronization with the windows XP home computer for contacts seems to still be ok, too regardless of the MS Exchange Versamail account commingling with my personal POP accounts.  Maybe the install sequence is overriding the previous posts' notation that MS Exchange mail definition will override synch with Palm OS Desktop?
    The problem now is I have a different/second home computer that's Vista os.  I installed the Palm OS Desktop and synch with the Treo.  The contacts list is not synching to this second home computer, maybe because I didn't follow the exact same sequence as for the Windows XP pc?  I can still synch my Centro with my Windows XP pc and that includes contacts.
    Is there a way on this second pc to override the MS Exchange contacts override for synchronization without having to go through the exact same install sequence as occurred on the Windows XP machine?
    Post relates to: Centro (Verizon)

Maybe you are looking for