I have a Windows 7 PC running IIS7.5 for its localhost. On this machine, I can successfully navigate to: localhost and ip-adress.
However, I cannot access this localhost website from another computer on other network
need Help?
localhost is only accessible from this very host, hence it's name. If you try to access it from another - you will be accessing this other one (client), not the one you intended.
Check Firewall. I guess you need to open 80 or 8080 port.
And use IP instead of localhost on another machine.
Related
Overview
Win 10 pro, 64bit
static-server works from localhost
All other node.js servers stop working on localhost,127.0.0.1 and only works on 172.16.xxx.xxx host
From the source I can see that static-server host is 0.0.0.0 which is the same as mine. I run my server on 0.0.0.0 https://nodejs.org/api/net.html#net_server_listen_port_host_backlog_callback
All this happened suddenly on my windows machine and on several web apps with webpack. I installed windows again and the issue persists.
I use WebpackDevServer with host : 0.0.0.0
Details
I'm running on a brand new win 10 with some vpn installed.
So I have these 3 apps
webpack-app on host 0.0.0.0:9080
static-server on port 9080 (should be localhost as well)
webpack-app with react-create-app on port 3000
I start the webpack-app on port 9080 and I go to the browser and says "This site can’t be reached,localhost refused to connect." (I'm 100% sure is running on 9080 because all my webpack apps stop working at once)
I now start static-server and runs on port 9080, doesn't complain at all! Now I go to the browser and it opens the page on port 9080.
So now I think I'm running on 2 different networks. Here is how it looks in windows:
So now I look if somebody is listening to the port 9080 and I see this:
I turn off the static-server and it disappears. Means that the static-server correctly shows up there.
Also there is no other node.exe process over there. So where did my webpack-app ended up?
Now after some times something popups there on port 3000
Not sure why there are so many on the same port, I go to that url and it works. But doesn't work from localhost:3000.
What is going on? why it doesnt work from localhost anymore?
If you use the Windows Subsystem for Linux, especially WSL2, keep in mind that it runs in a Hyper-V virtual machine with a virtual NIC. In other words, it creates its own virtual network.
According to the WSL2 FAQs:
the new architecture uses virtualized networking components. This
means that in initial preview builds WSL 2 will behave more similarly
to a virtual machine, e.g: WSL 2 will have a different IP address than
the host machine. We are committed to making WSL 2 feel the same as
WSL 1, and that includes improving our networking story.
As a result, the development server will run at a different address than 127.0.0.1 (aka localhost). This is why a connection refused error is returned when calling localhost from the browser.
Here is a possible solution, as suggested by Microsoft.
Ran into the same issues as above. Cleared my browser data and cache, it worked like a charm!!
So very strangely after a few restarts it just works. My node.js server listens on 0.0.0.0 instead of 172.xxx.xxx.xxx. I'm really confused as why it works now and why was not working before. If somebody can figure out would be wonderful. Thanks everybody for the help.
Edit: Happened again and I fixed like this: I disabled all my docker and expressvpn apps to start on windows start and restarted my pc, now works.
Edit 2: Happened again and I fixed by closing express vpn and disabling my wifi. I only use the wired Ethernet cable. No need to restart this time.
I think something is going on with my windows machine. Not sure why there are to networks.
I'm trying to host a website in Azure using Phoenix. When I use a browser in the VM to go to the website it works and nmap is also showing that the ports are open.
However, when I go to the website from my own PC I cannot reach it. I suspected this to be caused by the network security group settings so I opened the ports:
However, it still doesn't work. What else can be causing this?
EDIT: nvm I must have been asleep when configuring the security group settings. Thanks to Justin Wood for pointing out the wrong port number.
You already have port 443 (HTTPS) open. You will probably want to open port 80 (HTTP) as well.
Here's The Scoop,
I used SET (Social Engineering Toolkit) and made duplicite of a login page, the ip that was used was 10.0.2.15 (Mind you this is on a virtual machine Virtualbox), and when I tried to view it on another computer, it says the server is not responding.I tried to port forward but it was giveing me issues.
is there anything I can do to port forward or do something like that to make the web page connected to the IP viewable on the World Wide Web of another computer.
In other words, the IP's page is only viewable on the same computer who's ip I used to host, can you make it viewable on any computers browser by port forwarding it or something that will work like that.
Use bridging networking for the guest machine. Then, that IP address should be accessible on your network if there are no firewalls enabled.
There are several issues with directly accessing this IP from a separate computer.
First, the forwarding: the computer with the VirtualMachine must accept ip forwarding. This is easy to enable:
https://wiki.archlinux.org/index.php/Internet_sharing
Second, the routing: other computers must know who to ask when looking for 10.0.2.15. This is the hardest part. You could try adding a special route rule on the other computer, to set the host as a gateway for 10.0.2.15, but it requires you to make this on every machine that wishes to access the VM.
As Ahmed said, the easiest way is probably to use a network bridge, where the virtual machine will act as any other computer on the network, with a visible IP.
Context: i've set up a vm server for GIS testing and dokuwiki on the domain root. I'd like to serve the gis web apps on a subdomain so that dokuwiki url renaming will never conflict (and it just feels cleaner). I thought i had it solved with avahi-aliases, but then discovered...
Problem: I can't reach the subdomain from any windows pcs on the LAN. Linux VMs connect just fine. Am i trying the impossible or just doing it wrong? (i'm a DNS noob) Why would Linux find the subdomain but Windows not, even on the same LAN??
Setup:
i can't change anything on the corporate routers/servers.
VMs are on different PCs on the same corporate LAN.
VM1 (virtualbox, hosted on windows PC1): Mint 13
VM2 (virtualbox headless server, hosted on windows PC2): ubuntu server 12.04, LAMP, samba, avahi, avahi-aliases.
primary domain: vm2.local
subdomain: gis.vm2.local (configured in apache and avahi-alias)
What works:
I can reach vm2.local AND gis.vm2.local from vm1 (via ping and browser).
I can reach vm2.local from any windows pc on LAN (via ping browser).
What doesn't work: I cannot reach gis.vm2.local from any windows pcs on the LAN.
Any ideas or advice is appreciated!
Sounds like either a firewall issue or Apache/IIS (whatever is hosting your web app) isn't listening to all traffic (If you are actually sharing networks). Try a traceroute/tracert from the machines to the destination and see what paths they take. It's a little hard to troubleshoot without actually seeing how your network looks.
You can also test if your hostname resolves by trying a ping on the PC's having issues.
If it says "Ping request could not find host . Please check the name and try again" - It's a DNS issue and you can address it quickly by providing the IP of the machine with its hostname in %WINDIR%\system32\drivers\etc\hosts
I installed IIS on a laptop (win 7 professional 64 bit).
Created a website. I been able to view the website within the network.
If i type 192.168.0.227/vdv (local host ip address)(laptop's ip).
Now i need to access this website from outside the network.
I bought a WiFi modem and connected to the lap (now lap is disconnected from LAN). The modem has a dynamic IP & lap is assigned 192.168.100.100. Now i need to access the website which is in the laptop from outside the network .
How to do ?
If I am reading your post correctly, you are running IIS locally but you are having problems connecting when your local IP changes.
By Default, IIS binds to all IP addresses, so it really shouldn't matter if you use your LAN ip or Modem IP. Either way, for simplicity you should either be using localhost or 127.0.0.1 or your machine name as your address. This won't change when your local IP does.
First see if http://localhost/vdv works. If it does then continue to use that, otherwise you may need to change the bindings in your local IIS installation or your application. Make sure it's not listening on a specific IP address.
Take a look at this article for more information: http://blogs.technet.com/b/chrad/archive/2010/01/24/understanding-iis-bindings-websites-virtual-directories-and-lastly-application-pools.aspx