Could not connect to the remote computer make sure that the remote computer name is correct?

I am trying to configure Web Deploy 3.5 on Windows Server 2008 R2 Standard with SP1 installed on it. When I try to validate connection using Visual Studio 2013 to publish a website it throws the following error.

Could not connect to remote computer (computer name). Make sure Web Management Service is started. Learn more at http://go.microsoft.com/fwlink/?linkId=221672#ERROR_DESTINATION_NOT_REACHABLE

Could not connect to the remote computer make sure that the remote computer name is correct?
And I have tried everything found on all the forums as follows. And I have also done this before at a different job and every time it worked just fine.

  1. Made sure Web Management Service is started and set to Automatic
  2. Made sure that Web Deployment Agent Service is started and set to Automatic
    Could not connect to the remote computer make sure that the remote computer name is correct?
  3. Web Deploy 3.5 is installed
  4. I have tried installing different version of Web Deploy 3.5 too like the hosting versions.
  5. I checked if the firewall port for Web Management Service is listening on 8172 port (see image below).
    Could not connect to the remote computer make sure that the remote computer name is correct?
  6. The .Net Framework version I think that is not an issue.
  7. I have also made sure that during installation of Web Deploy 3.5 all the components are installed.
  8. When I click on the server node inside IIS and inside Web Management Service it also says Enable Remote connection
  9. I have also checked if users are delegated to publish on that website.
  10. I don't find any logs inside C:\inetpub\logs\wmsvc either.

I cannot ping the 8172/webdeploy.axd url. Is there any other service that could be listening on some port that I am missing. Something is odd here. I cannot see any traffic going through even Fiddler from my local machine. I have tried to paste the .axd url on the server's internet explorer and it still cannot reach it and doesn't say anything.

More Finding:

I tried to connect using Telnet client and it says: Could not open connection to the host, on port 8172: Connect failed. Somewhere it is blocked and I have no idea where to look for.

asked Jul 18, 2014 at 13:27

MitulMitul

2911 gold badge2 silver badges7 bronze badges

A comment on this answer at stackoverflow got me on the right track with this same error message if anyone else comes across this and the other answers don't help: https://stackoverflow.com/a/13871041/1128742.

Not only does web deploy need to be installed, but the IIS Deployment Handler subitem needs enabled. Open up Add/remove programs > Microsoft Web Deploy > Change > make sure IIS Deployment Handler is Enabled.

Could not connect to the remote computer make sure that the remote computer name is correct?

Web deploy was working for us then we applied some windows updates and it stopped working suddenly, this was the culprit.

answered Jun 21, 2017 at 13:56

1

I had the same problem (404). Fixed it by:

  1. Uninstalled Web Deploy 3.6 from Programs & Features
  2. Downloaded x64 package from https://www.iis.net/downloads/microsoft/web-deploy#additionalDownloads
  3. Installed downloaded MSI package, which turned out to be Web Deploy 3.5.

Immediately (without a restart) this resolved the issue.

answered Nov 3, 2016 at 4:53

AidanAidan

1411 bronze badge

1

I've just had similar problem. It was due to messing with SSL certificates.

During the installation of WebDeploy you normally install Management Service which creates self-signed certificate named: WMSvc-HOSTNAME.

This certificate should be available in Certificate Store:

Could not connect to the remote computer make sure that the remote computer name is correct?

and should be visible in IIS under Server Certificates:

Could not connect to the remote computer make sure that the remote computer name is correct?

Since I was messing with it somehow WMSvc-HOSTNAME was available in Certificate Store and disappeared from Server Certificates in IIS.

The problem was that Management Service was configured to use WMSvc certificate:

Could not connect to the remote computer make sure that the remote computer name is correct?

Solution:

Create new Self-signed SSL certifcate and used it with Management Service instead of WMSVC one.

answered Nov 2, 2016 at 11:01

Could not connect to the remote computer make sure that the remote computer name is correct?

1

So the issue turned out to be there was another firewall preventing any connection to 8172 port and it had to be opened up.

answered Jul 18, 2014 at 16:12

MitulMitul

2911 gold badge2 silver badges7 bronze badges

0

I had the same issue, posting my solution for completeness: I was trying to Web Deploy to a Hyper-V VM, resolved by re-creating the Virtual Switch used by the VM. Probably got misconfigured a while back trying to troubleshoot some other connections. Should've checked earlier if I could actually reach the destination...

answered Mar 9, 2020 at 11:47

Not the answer you're looking for? Browse other questions tagged windows-server-2008-r2 iis-7 deployment msdeploy or ask your own question.

How do you fix this computer can't connect to the remote computer?

Restart the Remote Desktop Services service on the affected machine. This can also be done remotely, open the Services Console on another server and right-click Services (Local), then select Connect to another computer, enter the name of the affected server, and click OK. RDP must work as expected.

How do I fix unable to connect to remote server?

Solution 1: Restart Driver Easy The problem can be caused by temporary disconnection from the server. When you run into this error, you can try to restart Driver Easy and see if the problem resolves. Solution 2: Ping Checking 1. Press Win+R (Windows key and R key) combination to open the Run dialog box.

Can T remote Connect to Windows 10 computer?

How do I solve problems with Remote Desktop in Windows 10?.
Check your internet connection. ... .
Check if remote connections are allowed. ... .
Remove your credentials from Remote Desktop. ... .
Turn off custom scaling. ... .
Change Firewall Settings. ... .
Make changes to your registry. ... .
Add the IP address and server name to the hosts file..

How do I resolve an RDP problem?

You can check to make sure that the Windows Defender Firewall service allows RDP traffic by completing these steps:.
Open the Control Panel by entering Control at the Windows Run prompt..
Click System and Security..
Click Windows Defender Firewall..
Click Allow an App or Feature Through Windows Defender Firewall..