I have no trouble debugging from Visual Studio 2010 when I go to work and wire into the LAN.
However, when I telecommute over the corporate VPN, I cannot debug, because when I try to debug, the monitor correctly shows a status of <datetime> CONNECTED, but Visual Studio 2010 comes back with the "Unable to connect ...The remote computer cannot connect back to this computer" message.
There is no change in procedure between debugging from home or debugging from work; it simply won't work over the VPN...
The remote machine is my VM running on corporate servers someplace. I can ping my developer machine from the remote virtual machine, and I'm using Windows authentication mode. Both machines are Windows 7 64-bit.
The application I wrote is deployed using the full-trust mode of ClickOnce.
Why?
Here's what was wrong:
Our corporate firewall allows remote clients to come in via SSLVPN and see everything at the corporation. What our firewall does not have is the reverse rule which allows computers already within the firewall to see remote clients as soon as they log in.
Therefore, the machine being debugged, which was running MSVSMON.EXE, could not see the machine running the Visual Studio 2010 debugger.
Related
This may look like a repeat of an already existing question but it isn't.
I am trying to work with an Azure-SQL database. I attempted to log in both from Visual Studio and SQL Server Management Studio and I get the following error:
Now, after some basic troubleshooting I made sure that the firewall in the server had my IP recorded, so that isn't the issue here.
Also, just for trying I did a mobile hotspot from my phone and it logged in with no issues. So for some reason my home network isn't letting me work this.
Now before I reached out to my ISP (which would be hell on earth) I did some more digging and found this: https://stackoverflow.com/a/38641107/6461236
That users suggests that the solution is to go into "SQL Server Configuration Manager" and modify port permissions. But when I attempt to find this, it's not in my PC. I have a Windows 10 PC and I have searched everywhere and I just can't find this SQL Server Configuration Manager. Check out what I get on my Computer Management window:
So the bottom line is that I have installed both Visual Studio 2017 and SQL Server Management Studio 2017 and my computer doesn't have a SQL Server Configuration Manager. After researching a bit more all that I have found is that it should be there.
What did I miss? How can I solve this pesky problem? Thanks in advance!
EDIT: Since I could log in with no issues with my phone as a hotspot and the issues only present themselves when using my home WiFi it seems that this is a problem with my home network and not with my PC or Azure. Any tips? Should a phone call to my ISP solve this?
The issue was that my network firewall was set to "max" and was therefore blocking any outbound traffic on port 1433 (which is necessary to connect to SQL Azure). The solution was to modify the router firewall to allow for communication on this port to be outbound.
I have a small home network of pc's all running Windows 10. None of the PC's have been or are in a domain. One (an intel NUC) runs Sql Server and my Surface 3 has Visual Studio. I use my Microsoft login for both. This setup has been running fine for almost 2 years.
Now I suddenly get the above error when trying to connect using integrated security.
Sql Authentication works fine.
I can also remote into the NUC and run SSMS without a problem.
I have followed the troubleshooting guide without success (KB 811889)
NTLM seems to be operating OK on the NUC.
I pinged -a IPAddress and it resolved correctly to the name of the NUC
SQL Server uses NT Service\MSSQLSERVER. I tried using LocalSystem but still didn't work
All the help articles I have found assume there is a domain or suggest Sql Authentication as a solution.
Only recent change has been installing Windows Update for Windows 10 Version 1607 on the NUC
Can anyone help me?
I want to connect my Windows 7 pc (Workgroup) to Server 2008R2 (domain) using hyper V.In server active directory is installed. I tried steps explained in http://community.spiceworks.com/how_to/show/30571-configuring-remote-administration-of-hyper-v-on-a-windows-7-pc .It didn't work for me.
EDIT
I am getting following error message when I tried to connect to server:
"Check that the Virtual Machine Management service is running and that you are authorized to connect to the server."
It is quite difficult to understand what is exactly your issue as you even don't mention any error messages which, I believe, you should get upon connection attempt. But generic answer will be following:
1. Disable firewall on machine you want to manage and ensure that you have network connectivity between management workstation and managed server.
2. After connectivity is confirmed run Hyper-V management console under account with appropriate rights on target server and try to connect to your server.
As for your spcecified error message and especially for scenarious when management workstation and Hyper-V server are not in the same domain or not in trusted domains (i.e. one or both of them in workgroup) this most likely requires extra configuration step on the management workstation: you should allow ANONYMUS LOGON to DCOM on the management workstation. This is required because WMI makes calls back from the server to the client. This is entirely expected (and is not Hyper-V specific). When a server is in a workgroup, the DCOM connection from the server back to the client is "anonymous".
To acomplish this do the following on the management workstation: Run (Win+R) > dcomconfig + Enter then in opened component services window expand the tree down through Component Services > Computers > My Computer, slect My Computer, right-click, choose properties and select the COM Security tab. Click Edit Limits in the Access Permissions area. Select “ANONYMOUS LOGON” from the list of users, and make sure Remote Access/Allow is checked in the permissions area.
You also should add user account you using to manage server into "Distributed COM Users" group on Hyper-V server.
For more detailed instructions with screen shots and overview of all prerequisites for Hyper-V remote management you may refer to the series of blog posts on Hyper-V remote management by John Howard: link to part 1 of this blog posts series.
I have two computers. One with windows XP where I have SQL Server 2008 Express and other computer with windows 7. In both computers I have sql server management studio.
Both computers are in the same work group. With explorer I can see the shared folder from one computer to each other.
In the windows 7 computer, when in explorer I put \myXPComputer I can see the folder that are shared and a conection that is sqlexpress. If I do doulbe click in this icon I get an error that say that windows can't access to \myXPComputer\slqexpress. However I can connect to the printers that are shared and they are in the xp computer.
So in the xp computer, I open sql server management studio and I try to add a new start session, but I only can see the location \myXPComputer, I can`t select other users from other computers in the same workgroup.
I would like to know kow can access to the database in XP from sql server management studio installed in my windows 7 computer.
Thanks.
In SSMS...
Server type: Database Engine:
Server name: the IP of the computer you're connecting to.
Authentication...
you can do windows, but it's harder to set up so let's not. So... make sure your SQL server supports mixed mode authentication and use the credentials of the SQL server you're connecting to, so if you're on 7 and trying to connect to xp, put in the IP of that xp box and the credentials that let you login to that xp box. Those credentials are probably SA. If not, make sure you have mixed mode & SA enabled.
This is the very basic jist of it.
I get the Exception: "General network error. Check your network documentation." when connecting to our new SQL Server 2008 R2 server. Nothing more that that I can tell about the exception.
In windows CE5 or CE6 (depending if using Motorola MC3090 or MC3190), Microsoft SQL Client 2.0 is installed (package sql.wce5.armv4i.CAB get deployed when running the application from Visual Studio 2008). I’m not able to connect to that DB on both version of the gun… I’m only able to connect with our Windows applications (x32 and x64). The connection string I use is the following: "Data Source=ip_address;Database=dbname;User ID=username;Password=password"
I successfully connected to a dev database in our LAN. The dev database server is also 2008 R2 SP1 but there are no port block (wide open). Apparently, nothing is blocked according to the sys admins. The new DB server is now virtual and remote.
Is it possible there is some kind of options to prevent connections from some sources? Is there any diagnostics tools I can use?
Any ideas beside that?
Thanks
That was finally my fault. When testing I left the gun on the cradle and connection failed that way... I needed to test with the gun not on the cradle using its wireless connection and it worked!