ASP.NET - Virtual PC - asp.net

I have created an ASP.NET application on my local machine. In order to test this application in IE 6, I have created a VPC. I am trying to connect to this web application through the VPC. However, I cannot connect to it. I can however connect to the internet.
What am I doing wrong?

Can you ping from the virtual PC? If not, you have network configuration issues.
Otherwise, check firewalls, and make sure that port 80 is open and sending traffic to IIS.

there are many possibilities. first I'd consider would be any firewall rules on the ASP.NET side preventing incoming HTTP connections.

What is the URL you are using to go to your site? If you are using localhost, you will need to change that to the actual IP address of your development machine, as localhost on the Virtual PC image will be a different IP address than localhost on the development machine.

Related

Accessing a web server on a Virtual Machine from another computer

I have setup a Virtualbox with a Linux environment running a web server. The host is running Windows 7, and I can access the web served by the server in the virtual machine from the host's browser.
However, I would like to be able to access this web server from another computer; say, a colleague on the same network that the host is in. Is there a way of doing so?
Summary:
Host (win7) interfaces:
- 172.16.1.15 (internet facing)
- 192.168.55.1 (VM facing)
Guest (linux with web server running) interface:
- 192.168.55.2
Web server is reachable from Host (through 192.168.55.1 - 192.168.55.2 interface)
Web server is NOT reachable from other computer on 172.16.1.X network.
Can you guys help me out on what I may be able to do in order to achieve this?
Thank you!
Well, despite downvotes without any kind of explanation why (thank you!), I have found a way of doing what I intended on Virtualbox settings:
On machine, right click, Settings > Network > Advanced > Port forwarding, and then, fill with corresponding data, i.e.:
host ip could be 0.0.0.0,
host port should be the port other users will use to access your computer (and thus the VM),
guest ip is the VM ip, and
guest port should be 80 if it is a web server typically).
Thank you, hope this helps to the next one running into this!

Making websites hosted in localhost "port" available to all on network

I have a website hosted in IIS in my local PC.
I can access to my IIS from other computers in the network by typing in http://my_lan_IP. However, when I try to get access to a specific port (http://my_lan_IP:8888) in my local PC, it says the "The site can't be reached."
I disabled all my firewalls and even tried allowing the specific port through Windows Firewall, but it didn't work. Viewing my IIS hosted site on other machines on my network
Thanks so much for your help :)
FYI: I am using Windows 10. My goal is to connect to the locally hosted ASP.NET website from other machines on the network.
Your web server needs to be configured to serve HTTP on port 8888 "for that particular website", in order for a client to connect to that port.
By default, your website is served on port 80, which is omitted from normal addresses. All http web addresses, if not specifying a port, is actually running on port 80, or 8080.
Your windows firewall will not effect local connections you make to your own pc. Get it working on your own machine, and then worry about firewalls that block connections from other machines on the network.
I was able to solve the issue by configuring a host header for a website. Thank you all for your help :)
https://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx

Can not connect to Azure web site hosted at VM

I deployed a web site into a Azure VM and did the following
1) Create a HTTP Endpoint with TCP protocol and port 80 (both
internal and external) for the VM
2) configure the web site to be assigned with the internal IP
assigned
I can browse to the site within the VM, but can not connect to it from external using either the DNS or the public VIP assigned by Azure. the browser said "can not connect to [vip]".
Have I missed any steps or any advice on how to trouble shoot this issue?
If this is a "normal" VM and not a Cloud Service then you need to connect to the VM and open port 80 in the Windows Firewall directly on the machine as well.
In the end, i found it is caused by the selection of "direct connect" at the Endpoint setting.
Untick it, it works...

Cannot connect to IIS using own IP

I am hosting an asp.net MVC 3 application on my local IIS 7.5 server. People can connect using my IP and the port I set. I can connect by typing localhost:port in a browser. If I type the IP:port however, the browser says it cannot connect.
Using wamp and other hosting programs (and even IIS at one point if memory serves), I could always connect using my own IP.
How can I set IIS to let me connect using my own IP? Or is the problem somewhere else?
My firewall is disabled, the port is forwarded and other people can connect just fine (people outside my LAN) and I have tried 3 browsers.
You cannot connect to your IIS using static IP, but, howerver you can by adding your Static IP as a lookup entry.
Please check this link:
How to Edit Your Windows Hosts File
The article explains how to resolve the IP to reach the IIS locally.

asp.net web page over vpn

I published a web application to one of app servers. Now, if I am connected within my company network (no login require), I can access the web site no problem. Now, if I am connected from outside of the network over VPN, I can't access the website (Getting page not found appears). Do I need to configure IIS on the app server for allowing the connection over VPN?
Thanks for your time.
It sounds like you do not have your firewall/router configured correctly to allow traffic from external sources. When your connected via VPN it is like you are connected to the internal network. Without the VPN you need to make sure it is routed correctly and visible through your firewall. Can you ping the IP that you are trying to get to?
Do you get DNS resolution when you connect over the VPN? If you are trying to hit an internal machine name address, you might try changing to the IP address of the machine.

Resources