I set up a local folder with WebDAV access (installed IIS, Windows Authentication, Authorization Rules, etc), and browsing to localhost will bring up a virtual directory of the path specified in IIS. Also, accessing this directory locally via the PC's IP works: for example, http://192.168.1.100/DRIVENAME will allow access to the directory.
When I try to access this folder remotely using the external IP address, the dialog box for username/password prompt is displayed, but the admin username/password does not allow access. For example, browsing to http://externalip/DRIVENAME will bring up the username/password prompt, but will not accept the admin credentials.
The designated port in IIS is set to the default 80, firewall rules for both TCP and UDP are set, and the port-forwarding is allowed on the router.
What am I missing?
Related
I have deployed my flask application on IIS using the IP address. I want to access this from another PC in the network, I have read about creating an inbound rule and allowing the access but is there a safer way to do this?
In my opinion, you could use the 80 port which is usually an open port.
if you want to use another port you can set the firewall and use the private only in profile:
after that, you could use iis IP and domain name restriction to restrict the other ip then the remote machine IP.
you can follow the below steps to allow connections from specific IP addresses:
1)Open IIS Manager
2)In IIS Manager, expand SERVERNAME > Sites > click on a required website > double-click IP Address and Domain Restrictions
3)Click Add Allow Entry... (on the right pane) to add an IP address or IP address range that will be allowed to access the website. Click OK.
4)Once allowed IP addresses have been added, click Edit Feature Settings... and select Deny for Access for unspecified clients. Click OK.
Now, only users with the specified IP addresses are able to access the website.
I'm trying to run my node app on localhost. After starting it reports that the app is running on localhost:8080. When I am on my home network I'm allowed to access my app on https://localhost:8080. When I am connected to work VPN or work wifi, my /etc/resolv.conf is generated differently and I'm no longer allowed to access my app on the localhost URL. I am able to access the app by giving the direct IP (which will not be 127.0.0.1 when I am on work network/VPN).
Please help me set my network configuration so that I can always access my app on https://localhost:8080
(Note that I am dependant on allowing automatic changes of my /etc/resolv.conf file to be able to access domains only exposed through the work nameserver.)
I have a website which is accessible via its URL but strangely i cannot connect to it via localhost on the server itself.
I have ensured that "127.0.0.1 localhost" is in my hosts file
I have checked that no other application is using port 80
I've ticked "Bypass Proxy Server for local addresses"
Pinging my local host from command line returns data When you go to the domain host URL the application loads successfully
Good news is my site is fully functioning but i just cannot figure out how to connect to it on localhost in my browser! any ideas?
Added details as requested;
Its a website not app if that was misleading.
The webserver is IIS on an Amazon EC2 windows instance.
The root URL is just a simple html page, which i can access via the domain URL.
However when i RDP onto the Server itself and try to access the localhost, it continually blocks me, the page wont load.
It is possible that your application is only listening on external IP address. To bind your application on all IP address, you may make your application listen on 0.0.0.0.
And could you please show the related code to help locating the problem?
Our web server hosts some APIs that other apps running on the same server need to call. These calls are failing with a 401.1 error.
The server has a single IP address. The server name and the network alias we use both ping to this same address.
I can browse to addresses on the server from other computers using either the machine name or the alias.
If I connect to the server I can't browse to any addresses using the alias. The machine name works locally but not the alias.
If I use the alias I am prompted to to login with my credentials. These are not accepted and then leads to 401.1 error.
How can I configure the server and/or IIS to allow the network alias to be browsed from the same server that the alias links to?
I am trying to connect to a FTP server hosted on azure VM using IIS I can connect but I keep getting the following error:
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Could you disable the firewall and try FTP to a different server?
Do you have an NSG (Network Security Group) associated with your VM ?, If yes then you'll need to open port 21/990 to access your FTP Server
Use Azure Powershell to setup the ports and check for the status.
Azure now have an FTP VM in the marketplace that fully setups FileZilla FTP Server https://azuremarketplace.microsoft.com/en-gb/marketplace/apps/cloud-infrastructure-services.filezilla-ftp-server
Setup instructions: https://cloudinfrastructureservices.co.uk/install-filezilla-secure-ftp-server-on-azure-server-2016/
You need to add an additional port range, which the ftp server will choose from for each ftp connection.
While the Windows firewall is automatically configured with rules for the ports 21, 990 and 1024-65535, when IIS FTP server is installed, the rules are not enabled initially.
To enable or change the rules, go to Control Panel > System and Security > Windows Firewall > Advanced Settings > Inbound Rules and locate three "FTP server" rules. If the rules are not enabled, click on Actions > Enable Rule.
https://winscp.net/eng/docs/guide_windows_ftps_server
Refer to the suggestion mentioned here: Cannot list directory on IIS FTP server on Azure, even after configuring Azure inbound rules and Windows firewall
Additional information: https://serverfault.com/questions/279286/how-to-resolve-ftp-error-failed-to-retrieve-directory-listing-for-administrato
If you are using passive mode the server opens a random unprivileged port above 1023. Therefore in order to work you would need to open up a range of ports in Azure. If you need this to work in passive mode your best bet is to use an FTP server where you can configure the passive mode port range, and then create the corresponding inbound port range rule in Azure (and in the OS). If you have any alternatives I wouldn't do it, since the fewer ports you expose the better.