I have 2 servers which are located in different networks. On each of them IIS is installed. When I try to connect to the first IIS server from the second, it gives me error: "Could not connect to the specified computer. The remote name could not be resolved". Fierwall is switched off. Maybe I should configure something in DNS or somwhere else?
Update:
Ping is ok, no packages are lost.
What happens when you "ping" the address from the command prompt?
If it comes up with host not found, then you either need to configure DNS on the server trying to get to the remote computer OR create a static hosts file entry pointing the name to the ip address...
Related
Suppose if my ip address is : 192.65.35.12. In this machine I'm running node server. I can access the webpages by using this url: http://localhost:3000/ in the same machine.
But, if I'm trying to access the node server from a remote machine having the ip 192.65.35.11. It does not work. I used the below url to access the url from the remote machine: http://192.65.35.12:3000/
I'm facing network connectivity issues.
Do, I need to change any settings in node.js for remote access.
Then, how can I access the node server from the remote machine.
if you can access localhost:3000, then type in 192.65.35.12:3000 on same machine. and if you are having problems connecting, then no outside computer going to connect. and you need to adjust your nodejs settings.
if you have server at home, and trying to connect from some place else not at home. you are more likely looking for something like "dynamic ip address" example: http://www.noip.com/ it helps getting past ISP (internet server providers) and your own routers, and publishing your ip address.
if you are dealing with 2 computers in your same house or business and passing through your own router, try changing the 192.65.35.12 to DMZ. basically by passing all router safety, if that happens, you are not opening correct ports on the router. or not setting other setting correctly.
I am trying to connect to a university server using a VPN client. I can connect to the client. Also, if I ping the server by name and by IP address, they both work:
ping servername
ping serveripaddress
However, I cannot access the server from the browser if I type:
\servername
\serveripaddress
and also I do not see anything in Network apart from my own computer. I changed my Workgroup to the correct Workgroup, and it still doesn't work.
Also, as my DNS suffix I use the domain name as well as the FQDN, but it doesn't work either.
I restarted after each of these changes, but it didn't help.
I read that when I have a VPN connection working and I am also able to ping the server to which I want to connect, it is most probably DNS resolution problem. But I do not know anymore what to do (I checked and tried the correct DNS suffixes).
Do you know what should I do more? I am using Windows 7.
Thank you.
It sounds like you're trying to use UNC pathing. Assuming that you're getting your network settings from DHCP, are you getting a WINS server?
I've a local website in my IIS 7.5 and the hostname I specified as samplesite.com and have added the bindings as * and the IP of my PC 192.168.1.2.
Also added the host entry in hosts file
Everything working fine in my local machine when I enter samplesite.com in browser. But my problem is I cant access the site from a PC in my same workgroup. How can I make it possible or what are the steps I've to do in both pc to make it work.
If you want to browse a website on another pc's IIS, you need to type 192.168.1.2/websitename from the remote pc.
First of all, you should check that the firewall, which is set up on the machine with the site, does not block 80th port.
Then you have two options:
you either remove host name from the bindings and use the machine ip (http://192.168.1.2) as the site url everywhere in your local network
or you have to add host enry 192.168.1.2 samplesite.com to hosts file on every machine where you whant to get access to the site. In this case you can continue to use http://samplesite.com url.
IIS FTP server stopped accepting connections, returning a "421 Service not avaialble, remote server has closed connection." error message after the instance was rebooted. The problem does not appear to be a firewall issue.
I had set up an IIS FTP server on an EC2 instance running Windows Server 2012 R2. Very basic, my boss just wanted plain FTP. I had previously set up an SFTP server on the same instance, using Cygwin sshd, that was working just fine. I set up the "default" IIS FTP server, and it was working fine for a few days, until during a file transfer, it hung. The CPU was pegged at 100%, according to the AWS monitor. I could not RDP into the instance, so I had to re-boot it. Ever since, I could not connect to the IIS FTP server. The "ftpsvc" process status is running, according to the task manager. I have stopped and started it several times. The Windows firewall is off, the AWS firewall has ports 20, 21, and 50,000-51,000 open. No settings, that I am aware of, have changed since it stopped working.
From a local command prompt:
> ftp localhost
Connected to MYINSTANCE
Connection closed by remote host.
From a remote command prompt:
$ ftp myact#xx.xx.xx.xx
Connected to xx.xx.xx.xx
421 Service not available, remote server has closed connection.
But SFTP works:
$sftp myact#xx.xx.xx.xx
myact#xx.xx.xx.xx's password: ****
Connected to xx.xx.xx.xx
I am not very familiar with IIS, and it seems to be running but I don't understand why FTP stopped working after the instance reboot. Note that the EC2 instance is using an Elastic IP, so its at the same public IP address as before the problem started.
I'll post here because this was a big headache for me too. I had to add svchost.exe to the windows firewall and everything worked.
http://youtu.be/l_sk5ITlICo?t=4m53s
Sorry, the problem turned out to be an incorrect setting in the IIS FTP-site Site Bindings. EC2 instances have 2 IP addresses, one private and one public. It seems that the FTP server was set with the EC2 instance private IP address, and when the instance re-booted, it got a different private IP, but was re-assigned the same public IP using the Elastic IP feature. Live and learn.
I've got CouchDB installed on my linux cloud server and I'm trying to access the "Futon Welcome Screen". The O'Reilly book says to go to "127.0.0.1:portnum", but I'm not working on localhost, it is my remote server, so I should be able to use "xxx.xxx.xxx.x:portnum" (my remote address) to access Futon right? This is not working, do I need a virtual host or something? Thanks.
Go to your local.ini file. (probably in /etc/couchdb) and set bind_address to either 0.0.0.0 (ie. respond to all IP addresses) or specify another IP address that you're either using in your LAN (private) or over the internet. (public)