I am communicating with a server behind Microsoft ForeFront and I am in need to connect to the Visual Studio Remote Debugger located on the server. My development computer is located outside of Microsoft ForeFront and therefor it is quite troublesome. So far I have managed to make the connection from Visual Studio on my machine outside forefront to the Remote Debugger on the server inside forefront. I can see in Remote Debugger Monitor that connection is successful. "DOMAIN\Jens connected" it says. The Visual Studio client is still waiting and after a while it complain "Unable to connect to the Visual Studio Debugging Monitor named Jens#SERVER. The Visual Studio Debugger on the target computer cannot connect back to this computer"
To set this all up so far I have tried to tunnel the remote debugger connection using Putty.
I have set up Putty to connect to a linux-server outside the Microsoft Forefront network. In Putty I have set up the following forwards (123.123.123.123 is the linux-server outside ForeFront):
4R123.123.123.123:135 localhost:135
4R123.123.123.123:137 localhost:137
4R123.123.123.123:138 localhost:138
4R123.123.123.123:139 localhost:139
4R123.123.123.123:445 localhost:445
This part works great. I can access all these ports from my development machine and as I wrote earlier Visual Studio can even connect. I have set up a local administrator on my development computer and on the server with the same username and password and I run both Visual Studio and the Remote Debugger using this user.
Now my theory here is that the Remote Debugger on the server wants to make a TCP connection back to my development computer to send a reply to Visual Studio and I guess my connections from visual studio to the remote debugger on the server would look like they have originated from localhost. I therefore guess that the Remote Debugger will try to connect to origin (localhost) and try to send the reply there.
Does this make sense? If so, is there a way I can spoof this connection as coming from the actual IP address of my computer? If that is possible maybe I can trick the Remote Debugger to connect to the right place?
If I have explained this in a bad way, please ask me and I will do my best to clarify.
Ok, I have now found a simple solution to this. I installed OpenVPN server on a VMWare virtual machine on my development box. So I now have tree machines.
My development machine
The server in need of debugging
A new OpenVPN server (virtual)
I then opened up port 443 in my firewall towards the OpenVPN machine and next I installed the OpenVPN client on both the server in need of debugging and on my development machine and connected both to the OpenVPN server.
I had to configure OpenVPN so that I had 2 different users (one for each client) and I also had to enable cross-user communication on the VPN. I just had to add the IP submet of the VPN to the allowed private network list.
One last bit was to add an entry in the C:\Windows\System32\drivers\etc\hosts file pointing the server name to the vpn ip address (you have to connect to remote debugger with correct server name)
Related
On my computer I have deployed my web site on IIS. If I access this website locally with :8080 works perfect, but when I try to access this site from another machine or my Android phone I get 'The site can't be reached. my_ip_address took too long to respond ERR_CONNECTION_TIMED_OUT –' this error.
I have tried solutions from this question, but nothing worked for me. Need some help!
There are few factors which can affect the accessibility of the site hosted on your local computer:
Is the client machine (including your phone) in the same network as the Server (In this case your site)
Is the firewall configured to allow connections on port 8080
Have you tried accessing the server using the IP Address. For e.g. http://192.168.0.1:port
Steps to isolate
Ping the server Ip from the client machine and see if it is able to connect to it.
ping 192.168.0.1
If the above fails, then I would assume that you are not on the same network. If it succeeds then check if the port is open.
You can also use nmap to see whether the ports are open or not
nmap -p 8080 kaushal.com
If the above fails, then open the port in your Firewall configuration and then try again.
Try this and share the results.
I can't seem to figure this out and hoping someone can give me some pointers. I'm unable to open a port on a Azure VM. After a fresh provision of a Windows 2008 VM I've disabled the Windows Software Firewall for all networks. Next i went to the azure management portal and added a TCP endpoint for port 9090 (both public and private).
While connected to the server via RDP i visit http://www.canyouseeme.org/ to test if port 9090 is open. But it comes back as error cannot see the port 9090.
As far as I can tell this is a standalone VM not connected to any domains or special networks.
Any ideas what is missing?
This was a strange problem that i "fixed" by changing the VM size from extra small > small and back again. For some reason something was reset and i could open the port again.
I run an ASP.NET Development Server (that came with MS Visual Studio 2010) on my Windows 7 machine. I'm currently developing an ASP.NET C# web application and to test it on Windows 7 machine I need to navigate my web browser to an address like this:
http://localhost:59215/Default.aspx
I also have the VMware Workstation 8 installed on that Windows 7 with other OS as virtual machines. I need to try to load my web app from those virtual machines, but when I type the above address there I get "Cannot display page" error in a browser. Note that I can access internet from a virtual machine itself, but for some reason localhost on the main machine is not accessible.
Any ideas how to set this up?
OK, I got it!
For those who're interested, here's how:
Say, my developement URL on the host computer is:
http://localhost:59215/Default.aspx
Download this util, called tcpTrace and run it on a host machine. When it starts configure it as follows:
Listen to port #: 80
Destination Server: localhost
Destination Port #: 59215 (which will be different in your case)
Click OK and let tcpTrace run on the host computer.
On the virtual machine navigate the browser to the IP address of the host computer, for instance in my case:
http://192.168.0.4/Default.aspx
and it will work!
PS. To get an IP address on the host machine, run ipconfig there (in a command prompt window). Your IP will be presented in the "IPv4 Address" line for network you're connected on.
PS2. Also my Windows 7 (host) doesn't come with any third-party anti-virus or firewall. It has a built-in Windows firewall and MS Security Essentials as an AVP. So if your setup is different one needs to open the incoming port 80.
PS3. Speaking of the VMWare Workstation, the virtual machine's network adapter setting is set on "NAT: Used to share the host's IP address" as it came out-of-box when you install it.
localhost is the local machine (to the OS).
I'm not sure if the VS dev server will allow external connections, you may want to install IIS - either way, you'll have to open up the Windows Firewall to allow external connections.
I'm no VMWare user but each OS will have its own IP address(?) - and that's how you'd connect to the Windows 7/IIS image. http://the.ip.address.of.the.win7.image/
I have SQL server running on a legacy Windows 2003 box on IP address 192.168.2.240. There seems to be a reference to the server with some old connection strings for a web application. I'm merely using it for comparison purposes because we just upgraded to Windows Server 2008, .NET 4.0 and Enterprise Library 5.0. The server is referenced with "SQL01" not the IP address. On the network where this IP address resides, I can ping "SQL01", but when I VPN to that network, I cannot. Why wouldn't this work over a VPN? This is a legacy server, and I don't know how it was setup. If anyone can explain where this name is configured, and how I can connect (or ping) "SQL01" instead of using the IP address, I'd like to be enlightened.
Try looking in your hosts file.
I have a Windows 7 machine hosting a Windows 7 virtual machine. I am developing a web application using visual studio 2010 on my host machine. I want to run the application in debug mode and access my localhost server from a browser on the virtual machine. (The purpose of this is to be able to debug an application that uses Windows Authentication using different users without having to log off and on for different users on my host machine...)
I am using a bridged connection for the virtual machine. I googled how to solve this problem and most of the threads that I found said that if I was using a bridged connection, I could access the server on the host machine by just entering the IP address of my host machine into the url in the browser of the virtual machine. I have tried some different urls using the IP but none of them have worked.
As an example, suppose I run my web application in visual studio on my host machine and its url is
http://localhost:62789/MyPage.aspx
Assume also that I ran ipconfig in CommandPrompt on my host machine and found out that the IP address for my host machine is xxx.xxx.xxx.x. What url should I enter on the virtual machine to access my web application?
Thanks in advance.
EDIT:
I set up IIS to host the web project. After that, I just added the following line (xxx.xxx.xxx.xxx is my IP) to my hosts file and I was able to access the website from the virtual machine:
xxx.xxx.xxx.xxx MyWebsite.net
I also had to edit my firewall settings.
I personally found it easiest to setup my virtual machine using the Microsoft Loopback Adapter, and assigning the virtual machine to that adapter. The Guest OS will be assigned it's own IP with DHCP. Using the Loopback Adapter will basically put your host and guest OS on the same network. The guest will only be able to access the host, and will not be able to access the internet.
You could then access the host from the guest using whatever ip address you see on the host(run ipconfig/all on the host).
Edit: FYI I am using Virtual PC so your milage may vary. THe Loopback Adapter is a free download from Microsoft.
Edit2: You will probably need to open ports on the host machine to allow access to the web server also. The guest OS's request will still be going through the Windows firewall
It seems like you might be using VisStudio's integrated Web Server. I'm not sure this can accept requests from any host other than localhost.
Remote machines cannot connect to Visual Studio web server
Simple solution? Use IIS to host the project. Once IIS is installed (if not already) it's easy to change the project settings such that a virtual directory is created and debugging occurs in IIS.