Problems conencting via Remote Desktop Connection to a server
hello! i have a problem connecting to one of our servers via Remote Desktop Connection. The story goes like this: the server works fine, i can connect using my credentials with no problems, the firewall is up. But, when i restart the server, after loading
windows, the server wont respond. I try to ping its IP Address and no respond. The only way so far to fix this bug is to log on localy (without remote) and disable the Windows firewall. Instantly the server starts to respond and i can connect to it via remote
desktop conenction. If i restart the server, the problem appears again and the solution to it this time is to enable the windows firewall back again. This enable/disable firewall thing doesnt seem right. Does anyone have any idea?
thank you!
Hi Dede,
Your box is up to date with windows updates.
Witch windows server are you using?
Maybe review the firewall exceptions.
Att,
Nicolas Rojas
Similar Messages
-
Trouble Printing to Network Printer via Remote Desktop Connection
Specs:
Macbook Pro, early 2013,
Mavericks (10.9.2),
Microsoft Remote Desktop Connection v.8.0.5 (latest),
Connecting to Windows Server 2008 standard
Printer, HP LaserJet P2035n, connected via the network
When on the Mac connected to the server, the printers from the Mac are redirected so you're supposed to be able to print from Remote Desktop to the HP printer. However, when you select something to print, the job goes to the print and keeps printing over and over and over again until you cancel the print job, which it usually allows you to do, or turn off the printer, which you have to do when it won't let you cancel the job.
Any advice on how to get the printer connection running normally?What you haven't told us is what method you use to connect/setup the printer on Windows. There are two ways - Bonjour for Windows (free software from Apple), and TCP/IP raw port 9100. If you have a problem using one, try the other.
-
Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008
I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
desktop software.
The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
software running directly on each employee's Mac Mini.
We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
dymo label printer requires a dymo label printer be installed and connected ..."
To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
Sorry for the long-winded question. I hope you can help me.Hi,
Thank you for posting in Windows Server Forum.
Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support -
Small problem: how using "Remote Desktop" on Snow Leopard Server
Hello,
How can I login to the Mac Mini Snow Leopard Server from 2 different Macs ?
Before I bought my Mac Mini Server in July, I asked the Apple Support if Snow Leopard Server has the equivalent of the Windows Remote Desktop functionality. He told me that it is possible. He did not tell me how, but I believed him.
I cannot find it in the documentation. Only 1 person can use screensharing. But I need more than 1 person working on the Mac OS X Server.
I moved our Photo library to the Mac OS X Server. With filesharing it takes 5 minutes to start iPhoto on our client iMac ( 1Gbps network). That is unworkable. So, from more iMacs users have to login to the server and start iPhoto on the server.
Thanks for the solution.
Hubert AnemaatAs per Jason's reply, there are two Terminal Server products available for Mac OS X. I have been testing both, both work in the same sort of way and will allow multiple simultaneous users to connect.
The typical approach is to (obviously) first to install one of these Terminal Server programs on your server. Then you (ideally) need another server hosting your Mac network home directories, and it needs to share the network home directories via NFS rather than AFP.
Note: Due to the way Mac OS X handles mounting AFP shares, you cannot have two users using the same share at the same time as the login defines the privileged's and the first logins privileged's would not be suitable for the second user, this is also why you cannot use "Fast User Switching" with two network login accounts when using AFP.
So, a client uses an RDC client (e.g. the free Microsoft Remote Desktop Client) to connect to the Terminal Server, this initiates a network login which access the users home directory via NFS.
RDC client (Mac or PC) ------> Mac Terminal Server <------ Mac network home directories
I have not tried iPhoto, but have tried various other applications, e.g. FileMaker, AppleScript, Microsoft Office 2004, etc. and the only problem I have hit so far is that Visual Basic in Office 2004 generates errors but Word and Excel otherwise work. Remember Office 2008 does not support Visual Basic (i.e. Macros).
I would actually expect iPhoto to work for multiple users as long as you use NFS. Using NFS for network home directories rather than AFP has actually 'fixed' a couple of badly written applications that had problems with AFP based network home directories, e.g. Adobe Acrobat 9.
I am using Mac OS X 10.6.4 Servers. -
Remote desktop connects, black screen, disconnects after a few seconds
I have several servers running Windows Server 2012 R2. These servers are used for testing, and are members of a domain which has two DCs, each of which are running DNS Server.
Yesterday I noticed one of the servers was having an issue with its remote desktop connection. If I try remoting into this machine, it connects to a black screen, sits there for 2-3 seconds and then promptly disconnects. No error message is given. I tried
this from a couple different Windows 7 machines, and got the same result. I tried from my wife's iMac, which runs Jump Desktop, and too was met with the same result.
I can, however, remote into this machine via RDP from my work-issued laptop, which is running Windows 8. However, I cannot remote into the problem machine via Remote Desktop Connection from one of the 2012 R2 servers--I am met with the same result as the
other machines: connect, black screen for 2-3 seconds, disconnect without error.
I can remote into all of the other 2012 R2 servers without issue from any machine, including the iMac. I am experiencing this problem on one server only.
Since it is a test server, I reinstalled Windows from scratch this morning. This meant formatting the SSD and wiping everything out. I reinstalled the drivers, joined the server back to the domain and installed all of the updates available from Windows Update.
And rebooted. And yet, the problem persists!
I tried troubleshooting the "usual suspects," like turning off Windows Firewall, disabling antivirus software (currently none installed), disabling IPv6, setting a static IP instead of using DHCP, etc. I did notice the network adapter said it was
on a Network, not a Domain Network. I corrected DNS settings, and the network reidentified itself as being on the ParietalBone.net network. And yet, the problem persists. Remote Desktop to this server still yields a black screen for 2-3 seconds, followed by
a disconnect--EXCEPT from the aforementioned Windows 8 machine.
I looked in the TerminalServices-LocalSessionManager log on the offending server, and there are no errors. I only see repeated entries that say "Session X has been disconnected, reason code 12," where X is 1 or 2. On a couple occasions, the reason
code is 11. But I don't see any errors indicating a breakdown in security negotiation.
Without any robust logs or debug details, I'm at a loss of where to look for a solution.I am cautiously optimistic that this may have been resolved.
The network card in the computer was only a 10/100 built-in card, so I replaced it with a 1Gbps card. Interestingly, this did NOT resolve the issue. I ran netsh to check on the state of the chimney offload, but it was already disabled.
In the network card properties, I changed the link speed and duplex from automatic to 1Gbps full, re-ran "netsh int tcp set global chimney=disabled" and rebooted. The problem persisted.
And so I went to the network card properties and set IPv4 Checksum Offload, Large Send Offload (three of these -- IPv4, v2 IPv4 and v2IPv6) and TCP Checksum Offload (IPv4 and IPv6) to Disabled. Jumbo Frames were also disabled. I rebooted again.
After the subsequent reboot, I was able to connect to this Server from machines that previously gave me difficulty. The only machine I haven't been able to test today (I'm in the office) is my wife's iMac, which is at home. However, I was able to bring this
server up via Jump Desktop on my iPad, so I'm suspecting that perhaps one of the offload options was to blame. I'm not sure why this would allow me to connect from some machines but not others. And as noted above, I have many other machines running Server
2012 R2 and they are NOT experiencing this problem. And I've not done any tinkering with network settings on any of them, so their chimney and offload settings are all in the default configuration.
Regarding the other items -- NIC team, virtual machine, etc. -- there was no NIC team, no SRIOV and no RDMA involved.
I had to turn IPv6 off on this machine, and only on this machine, because having it enabled was causing a lot more problems. DNS registration would keep failing, it couldn't pull Group Policy, it couldn't get time sync with the DC, etc. The servers are all
set up with static IPv4 addresses. The router supports IPv6 but I'm not actually using it, so disabling IPv6 wasn't a concern to me. -
I have successfully to installed the RDS 2012 Server R2 per user CAL (5pcs) Open License after is found not allow over two users to remote desktop connection on this Server problem, I try to uninstall the license and then (internet on-line & telephone
call Microsoft Activate Center get the activate key) to reinstall is still same of the result on below problem.
Select a user disconnect so that you can sign in.
There are too many users signed in
User1 Active
User2 Active
() Force disconnect of the userHi,
In addition you can also refer following article for RDL configuration.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Scenario:
Windows Server 2012 R2 Essentials
I purchased an SSL Cert from GoDaddy and I managed (after some challenges) to set up Anywhere access to use that new SSL Cert. I to rebooted the server and I am able to login to Anywhere Access vis https (using the SSL certificate) from PC, Mac and iOS.
So far so good.
The problem I am having is that when I click to launch a remote desktop connection to the server RDP connection wants to use the self signed SSL certificate of the server rather than the SSL Certificate I installed into Anywhere Access. As a result, I get
a security warning like this: "The identity of the remote computer cannot be verified. Do you want to connect anyway?"
The name in the certificate appears as ACME-SERVER.ACMEDOMAIN.local instead of the SSL Certificate I installed, which is
remote.acmedomain.com
If I lick to accept, RDP does work fine, it;s just using a self signed certificate. I want it to use the trusted certificate that I purchased and installed.
My guess is that there must be an additional step to tell Anywhere Access that when it generates the RDP session that it should use the cert? OR, is this just how it works?Because....
the server does not have a 'trusted' certificate assigned to it.
Only the RDP Gateway has the trusted certificate for the external name.
If you want to remove that error, you have to do one of the following:
Make sure your domain uses a public top level domaim, and get a public trusted certificate for your server.
So, something like,
server.domain.publicdomain.com
Or,
Install that certificate on your remote computer so it is trusted.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+ -
Remote Desktop connection and retina display
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop. it's really important that that this staff works as good on my new computer. The problem is that when I open the connection on MacBook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, making it bigger or smaller but the display is still not great. Any suggestions or advice would be greatly appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.Should I assume from your reply that the solution lies with my corporate IT?
-
Remote Desktop Connection keeps disconnecting
I have BT Hub 3 (recently upgraded to Broadband Unlimited at the end of Jan 2015).
Up until recently I was able to Remote Desktop into my work computer (via VPN tunnel) with no problems at all.
Around March 6th, I began to experience problems with the Remote Desktop Connect (RDP), in that it now makes an initial connection and then disconnects (typically within a few seconds, occasionally after a couple of minutes).
It will then cycle through a number of reconnection attempts, all with the same result, before it finally drops altogether with the message:
'The Remote Desktop Services Session has ended. Connection to the remote computer was lost, possibly to network connectivity problems'.
I have tried restoring both machines back to a date when i know the connection was working - no joy. I've also tried deleting an re-creating now VPN and RDP connections - no joy. I've researched online and tried various other things, but still have the same problem.
I've tried connecting using a laptop (via my wirelss connection) with the same result. My manager has RDP'd in from his home machines and has had no problem at all.
This leads me to consider whether the problem is with the router/BT Hub itself. I've tried the online diagnostic tools with no resolution to this problem.
Has anyone else experienced the same problem?Oh well, I suppose that after more than 2 months of frustration with this issue, the BTCare Community is unable to help me.
I can be fairly sure that it's not my machine as it's also happened using a laptop, plus I've even reset my PC right back to its original factory state just to sure that nothing had become corrupted.
The network guys where I work have also looked at this and can find nothing at that end to cause this problem.
I've even borrowed another BT Hub and tried it through that - same problem.
So where does the answer lie? VPN issue? I've tried other VPN options - same problem. RDP problem? I've practically exhausted the list of suggested solutions that can be found by trawling the internet.
I even upgraded the broadband cable to replace the cheap old thing that has been working perfectly well in terms of broadband, again, to eliminate this as a possibility. Now I'm stumped.
To me, it looks like the problem lies between my router and the workplace network, i.e. a physical problem among the miles of lines connecting the two. Of course I don't want to shell out for a BT engineer to come out to investigate, so I thought that the combined wisdom of this community may have been able to help.
Sadly not. -
L7580 net printer driver disappearing in Win 7-62 after connecting with Remote Desktop Connection
I have an Officejet Pro L7580 connected via ethernet. I've been using the driver released from Jan 2010, and whenever I connect to my Windows 7 Ultimate 64 computer via Remote Desktop Connection, the printer drivers for both the printer and the fax disappear. I have to constantly run the "add a device" window to add the printers back again.
Why do they disappear like that?
FishandersonOK after updating the Server and clients I am still having this issue :(
and just today after no sound problems for 6 days the sound dropped out on a couple of RDP sessions, yet the sound on the client itself worked fine when tested (minimise the RDP session).
It took the RDP sessions to be restarted to restore the sound within the session.
I have found similar (old) thread regarding this problem:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/958fd891-6f55-432b-8268-a326ac6b2b2e/sound-in-remote-desktop-session-stops-working
but no one has informed about if as solution was ever found. -
Sound problem... when I try to use FL Studio via Remote Desktop Connection with a Windows XP laptop.
Hi Crimsonrain,
What is the model number of your router? -
Remote Desktop Connection not working
I am able to remote desktop connect to my home computer from work; however, I can't remote desktop connect to my work comptuer and server. I believed it has something to do with my Linksys E3000 access point settings but I'm not sure where to look for and verify. I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network. I also VPNP in to my work place so that it has the same IP address as at work and still, remote desktop connection from home to work is not working. Any suggestion is much appreciated.
thebluemamba_24 wrote:
Connecting from home to your remote desktop server has nothing to do with your router. Certain ports are needed to be opened from the server’s end in order to host an application. Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work. In case it will not work, then contact your IT guy.
If you read my previous post it said:
"I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network."
I think my above statement answers your question of "Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work." However, your statement prompts me think of something else. What I have tried is bring my laptop to work and tried connect via RDC to the server and it works but it just not working when trying at home. What I have not done is instead of brining my laptop to work and try RDC there, perhaps I should I try it on a friend's or relative's network and see if I can do RDC to my server at work. If this does not work as well, then, could it be that at work there is something something outside RDC coming? But even if this is so, why can't VPN work? -
Remote Desktop Connection to VM does not work after sysprep
Hello altogether.
Often asked, but never answered with an applicable solution!
What shall
we
do if
we
get no access to a Azure VM via Remote Desktop
Connection?
Everything went well: access to the VM via RDC was working perfectly!
Then
the idea came into
our
mind to create an image of the VM by use of the Azure Management Portal.
We
found that
we
had to apply “sysprep”
on the VM.
We
did it.
Then we did not take the image and decided to go on with the VM.
But if we start the VM we get no access via RDC!
We tried to find a solution by reviewing the already published contributions by other Azure
users. But none of the replies marked as answered supply with a qualified solution.
So can one provide a really applicable solution to us on how to arrange the further use of the VM?
Thank you in advance.There is an issue right now where the VM may start unexpectedly after you have run sysprep and selected the shutdown option (which is normally what you should do).
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown?forum=WAVirtualMachinesforWindows
But regardless of that issue - you can't use that deployed instance of the VM after you've run sysprep on it. It needs to stay shutdown, then you select Capture to create an image from it.
If you start it back up, either intentionally, or it is started unexpectedly because of the issue above, it will be sitting at the first interactive screen of setup. RDP is not working at that point, and since there is no console access to an Azure VM, there
is no way to get past that prompt.
For other scenarios, you might be able to attach the OS disk of that VM as a data disk to another VM, and while you could do that in this case too, there is no supported method for disabling sysprep at that stage of setup.
So while you could attach it to another VM to get data off of it (you would have to remove the VM first), the VHD is no longer in a supported state to use as a VM itself.
Thanks,
Craig -
Remote Desktop Connection fails
I have a new Server 2012 R2 essentials install. I have tried connecting with remote desktop connection but have no success.
I can connect to the server at the local desktop. From any other computer on the network it fails.
I have checked a plethora of things I found on the internet but with no luck.
I have tried to connect by ip address, no luck.
I can ping the server just fine.
I cant find anything of help in the event viewer logs.
Any help appreciated.Did you get any error message when failed to connect the server via remote desktop connection? Please use an administrator account to connect the server via remote desktop connection and check if the same issue still exist.
Remote Desktop goes to: Initiating connection for about 15 seconds, then I get:
Remote Desktop cannot connect to the remote computer for one of these reasons:
1. Remote access to the severe is not enabled.
2. The remote computer is turned off.
3. The remote computer is not available on the network.
In the Windows Server 2012 R2 Essentials, please follow the path: Control Panel-> System-> Change settings-> System Properties-> Remote and check if select "Allow remote connections to this computer" option.
I checked, it was already set.
In addition, please also open Group Policy Editor and follow the path: Computer Configuration-> Windows Settings-> Security Settings-> Local Policies-> User Right Assignment-> Allow log on through Remote Desktop Services. Add that correct
user or group, then check if this issue still exist.
I checked, it was already set. -
Remote Desktop Connection certification issue with Win Server 2008 R2
When connecting to Windows 2008 server R2, from Windows 7, Vista and Mac OS 10.6.7 via Remote Desktop Connection, i am getting a 'Server Name on the Certificate is Incorrect' error.
if i click connect, i can still connect to the machine, due to a 3rd party managing the server, this doesn't look very professional on my part...
The server is a standalone machine and is not currently on a domain. RDC is only used for management purposes.Hi,
This certificate error is normal, because your client do not trust the certificate which is installed on the terminal server. To avoid this issue,
you can export the certificate and import this certificate into the client side (computer account).
Thanks.
Maybe you are looking for
-
Screen output without connection to user - Work flow
Hi, i have created a workflow, it has a task which refers to a method which call a BDC in N mode, but workitem is not generating, in event trace showing RFC status 'Screen output without connection to user'. Same time i observed in ST22 for any dump
-
Windows xp does not recognize ipod
windows xp will not install ipod video...keeps saying it will not install ipod...tried to turn off norton...tried to uninstall itunes...changed drive letter...still will not install
-
I am working on two macbooks and an imac. I upgraded all the software last weekend and am now running all three computers on Lion. Over the last week, about 50% of the time when I click the mouse (whether it be the "pad" mouse on the macbooks or th
-
How do I open Word documents with docx extensions when I have Word 2004
How can I open Word docs with a docx extension when i have Word 2004? I tried Open XML format files but can't get it to open. Can I save the file in the old Word extension?
-
SYSFAN doesn't control the 3-pin's fan speed
Hi! I have exactly the same problem (BIOS version : 1.5) No solution ? Update to latest BIOS ?? Thanks