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!
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 just installed a Windows 2008 Standard R2 server with RDS. Whenever I attempt to connect to the server via RDP from a Windows 2003 server, I get the following error.
I am however able to connect from a Windows 7 desktop and using a Linux RDP client.
Anyone know why I'm getting this error and how to resolve the problem?
Thank you in advance.
This is probably a Server Fault question, but none the less my guess is the server has the following setting:
Maybe your Linux RDP client doesn't support this functionality?
If not, check your Firewall, it needs to look like this:
I am using the Liberum Help Desk as a Service Request System. It is host on a server that is running Windows Server 2008 R2 32-bit. I configured it with an Access database. It works well. Now, I am trying to shift it to another server running Windows Server 2008 R2 64-bit. At the beginning, I have an error with the JET driver, because there is no JET driver for the 64-bit machines. I fixed it by enabling 32-bit option in the advanced settings of the application pool. However, I am still facing a strange problem which is the following:
When I tried to browse the system that is on the new server (64-bit), it will redirect me to the system hosted on the old server (32-bit) and I don't know why. I checked the code to see if there is any link or something for redirecting me to the old server and I did find anything.
So how to fix this problem? what is the reason of it?
Finally, I found the solution. The problem was with the Access Database; there is a table called config and inside it there is a column for determining the link. I changed the link there and everything works fine.
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 need help. I wrote simple sink by sample in http://msdn.microsoft.com/en-us/library/ms998610.aspx. On IIS Smtp Windows server 2003 it work fine. But on IIS Smtp Windows Server 2008 or 2008R2 it don't work. I try other sample from Internet. None of them don't work on IIS Smtp Windows Server 2008 / 2008R2. Any idea?
Windows Server 2008 has a newer version of IIS that has full integration with ASP.NET. This is the default mode. You can switch back to the older (ASAPI ASP.NET) by changing the application pool in IIS from "default" to "classic". That should make your app run like it does in Server 2003.
Without seeing more code and details, that's the only thing I can suggest.