Yesterday we had a major problem with our windows 2003 webserver and we had to move all our sites to a new machine. There were a couple of sites that used a SSL certificate and we cannot export these because the we cannot start windows on the broken machine.
Is there a way to get these certificates to work on the other server? I have access to the hard drive of the broken server. I may have to mention that the new server is on windows 2008 r2.
Related
I have 3 RDP's (2 of Windows server 2012 R2 and 1 Windows Server 2008 R2). By using Microsft Remote Desktop, I am able to get connected remotely with the two Windows Server 2012 R2. But I am unable to connect with Windows Server 2008 R2. I am getting the below error.
Previously I was able to connect with all three. Also, I want to mention that in the windows environment I am not facing any issue with the RDP.
I am stuck to it and don't know what to do. Any help would be highly appreciated.
I had this issue and this is what I did to get working back the RDP client on a Macbook pro mid-2015 with the last big sure release.
First make sure that :
the remote server IS online
the remote server IS accepting RDP connections
the remote server firewall IS configured correctly with the right port
the remote server IS NOT configured to accept only connections with NLA
After validating the above points, then on your client (the Mac) you can try to get working the RDP with this first step :
remove (please make a backup) the file UBF8T346G9.com.microsoft.rdc located in /Users/[Your username]/Library/Group Containers/ then reboot your Mac.
If it still doesn't work, you could try to remove the app, reboot, then re-install the app again.
You can also analyze the Event-Viewer on the 2008 R8 server to see if there is something to help you to spot the issue.
More information about troubleshooting RDP :
https://learn.microsoft.com/en-US/troubleshoot/windows-server/remote/troubleshoot-remote-desktop-disconnected-errors
I faced the same problem some years ago.
here's the solution:
Read the article carefully. https://learn.microsoft.com/en-US/troubleshoot/windows-server/remote/troubleshoot-remote-desktop-disconnected-errors.
And check if the remote server IS accepting RDP connections.
And also check if the remote server accepting only connections with NLA.
delete the file UBF8T346G9.com.microsoft.rdc and Reboot.
And if still doesn't work, then totally uninstall / remove the app and install again and check.
Thank You
I've got a strange situation. Hope someone can help. I've got two independent IIS FTP servers.
IIS 7.5 runs as standalone VM
IIS 8.5 runs on a windows server 2012 R2 VM
When I connect to these ftp servers using FileZilla client (or the pftp client on ubuntu), both work as expected, really well. Passive mode, no problem.
When one of my customer's linux client is connecting, it works great on the IIS 7.5, but it does not work on the IIS 8.5
It stops after the PASV command with a timeout. The linux client is running a custom app on fedora which has FTP functionality embedded in it.
For authentication i'm using IIS Manager Users.
Does anyone have an idea of what this could be? Or how to troubleshoot this?? I can test, and see everything working, except when the clients processes are entering the scene!
Developing an MVC application, i now need to have test other browser versions.
Installed the VM XP on win 7. That is running good. Got IE8 installed and FF 3.6. I know IE9 has a compat mode for 8 and 7, but read some articles that these may not run exactly as their stand alone versions. I got IE8 installed on the VM XP, so now i need to connect to my IIS Win7 localhost.
IS there anyway to do this? and How?
You need to configure your HOST PC's firewall to allow the VM (and perhaps other machines) to connect on port 80.
You can then navigate to http://hostmachinename in the VM.
Although my firewall was off, i was able to connect using the local machine name or ip address, as stated above by SLaks. So, if anyone has there firewall on, you may have to allow the VM to access the ports.
I did set the VMXP >> Tools >> Settings >> Networking to my Nic/ethernet card.
Not sure if this had any effect.
I also had trouble at first not getting the .NET MVC website to run. But then realized our web.config is setup to take only https. I had my website running on 2 ports, one for is for SSL. When i use the https secure port, it connected. So iguess the web app was seeing the VM as another computer tryingto coinnect, that was not local, so it required it to connect by https.
I had a base Windows XP with IIS hosting some websites and it has been working for years, yesturday I upgraded to SP2 (which includes the security suit) because I needed .NET 3.5 and since then no one can access the web pages anymore.
When I connect to the macine locally and try to access the webpage it prompted me for a username / password - when I entered it I was able to access the page locally.
However, remotely I always get "Internet Explorer cannot display the webpage"...
Anyone know what I need to do so that we can access the pages again?
Thanks,
You need to open port 80 on the firewall. Alternatively, if you box is behind a hardware firewall, just turn off the windows firewall.
add an exception to the windows firewall settings for that IIS Application (port number if other)
I'm using IIS 5.1 in Windows XP on my development computer. I'm going to set up HTTPS on my company's web server, but I want to try doing it locally before doing it on a production system.
But when I go into the Directory Security tab of my web site's configuration section, the "Secure communication" groupbox is disabled. Is there something I need to do to make this groupbox enabled?
That is because IIS 5.1 under the limited Windows XP version is limited to only HTTP. You need to have a full version of IIS 6.0 on Windows 2003 to do this. Luckily you can download a VHD image of Windows 2003 from Microsoft and run it under a Virtual PC instance. Plus I would recommend this since you are trying to be careful and use a machine close to your production environment. IIS 5.1 version is never deployed as a production machine so you cannot guarantee anything and the differences between IIS 5.1 and IIS 6.0 are significant enough where the VM is worth your while.
You may need to manually create a certificate first (on WinXP there does not seem to be a built-in mechanism, so you need to use OpenSSL). Check out these two links:
Enabling SSL in IIS on Windows XP Professional
Enabling SSL (HTTPS) for IIS in Windows XP