I have simple web service (asmx) running on my PC using port 7778.
I've assigned the app pool (v2), port forwarded 7778 on my router to resolve to my local IP address (192.168.1.2) that I've set up manually (static local ip address). I've also used NoIP's service for DNS and this is checking if my non static real Ip address changes.
when I try to connect to:
http://mynoipdnsname.no-ip.biz:7778/Service1.asmx from any computer outside my local network
It's all working,
using:
localhost:7778/Service1.asmx or
192.168.1.2:7778/Service1.asmx
from my local PC works fine.
The problem is that when I try:
http://mynoipdnsname.no-ip.biz:7778/Service1.asmx
from my local computer (192.168.1.2)
it's not getting the data.
I have Android app, when I try to add web service's url:
http://mynoipdnsname.no-ip.biz:7778/Service1.asmx
I get error message:
Unable to connect to the remote server No connection could be made
because the target machine actively refused it
Any ideas what I've missed?
Thanks in advance.
P.S. My windows firewall and router firewall are turned off.
Add mynoipdnsname.no-ip.biz to your hosts file or your DNS.
Related
I'm developing an UWP app which needs to be the server for a win32 client application, which is not to be changed if possible. Now the problem is I can connect to my uwp server application if I connect to the hostname or IP address of my computer. In contrast if I use localhost or 127.0.0.1 I can't get a connection.
I'm running this command constantly to enable the connection without running it, it doesn't work at all. "CheckNetIsolation.exe LoopbackExempt -is -n=Packagename"
I also executed some tests, and found out that on the computer under company IT, it only works when using the IP address. Therefore with the identical setup on a computer which is not under the companies IT, it works as expected.
So I expect there's a problem with the way my machine is configured.
We have an proxy for all outgoing connections. Another thing when I use a win32 server and client I have no problem to connect to localhost, so it seems that my machines dns configuration is in general right.
Do you have any ideas how to torubleshoot this, or what I can try to find out where my connection attempt is going. Maybe the UWP application is trying to connect over the proxy?
I created a website on IIS at 192.168.0.163, and published a wcf service application on it, I can get wsdl of service through hostname hostname:port/Service.svc?wsdl and ip address 192.168.0.163:port/Service.svc?wsdl, but hostname.domain.com:port/Service.svc?wsdl not work, on another computer in same domain.
At the end of wsdl, I found the service address is ws://hostname.domain.com:port/Service.svc.
In client, I added service reference by vs2015, in app.config the service address also is ws://hostname.domain.com:port/Service.svc, and I can only connect to service from local computer which IIS stays, calling from another computer will cause a exception:
The remote endpoint requested an address for acknowledgements that is
not the same as the address for application messages. The channel
could not be opened because this is not supported. Ensure the endpoint
address used to create the channel is identical to the one the remote
endpoint was set up with.
If I change address to hostname:port/Service.svc or 192.168.0.163:port/Service.svc, then I faulted to access the service from both computers with same error.
Close firewall can't solve the problem.
How to make this work?
Solved after add hostname in IIS bindings.
I am maintaining our Nominet domains through their EPP System.
To do this is I am instantiating a TCP client and connecting using an ssl stream, everything is working fine locally in my virtual machine using both IIS and IIS Express.
However, when I deploy to our test server I get the error message "Authentication failed because the remote party has closed the transport stream".
I have tried disabling the firewall, and running fiddler but neither have helped, anyone got any ideas?
Just an update for anyone else who is struggling with this.
The issue is that with Nominets EPP system you have to specify the public IP address of the server you are running the EPP code from for security purposes.
As we are behind a firewall my development machine public IP and server public IP are the same therefore I didn't think I needed to change anything.
However, I noticed that when I was finding out my public IP for my dev machine it was shown as IPV4 and the test server was shown in IPV6 format although both had the same IPV4 address wasn't sure how I could get the test server to report its IPV4 address therefore simply added both IPS to Nominet and it now works fine.
Thanks
Ant
I've managed to get my WCF service working on IIS express and IIS locally via localhost. I was wondering how I can deploy the service so that it can be accessed outside my network i.e http: // public ip. I've done a lot of digging around and can't seem to find the right answer.
I've tried setting the IP bindings on IIS to my public IP but I get 'Bad request - invalid hostname'.
I have opened all necessary ports and host my own apache server which is accessible outside my network, so I know that the ports side of things is fine. I'm just having issues with the server hosting (IIS).
Any ideas how this can be achieved?
I am working on a big enterprise environment. When i try to deploy my solution to remote sever using ms build i get this error every time i try to deploy the app.
According to the error message it says it cannot connect but i can ping to the ip. I have even added the host ip and names in both machines host files. I don't know if i am doing anything wrong has anyone come across this before.How did you overcome this?
Note: i have replaced my ip with myip.com... and site name as my site name in this question.(My app is Asp.net MVC 4 Application)
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets (3847): Web deployment task failed.(Could not complete the request to remote agent URL 'https://myip.com/msdeploy.axd?site=my site name'.) This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server. Error details: Could not complete the request to remote agent URL 'https://myip.com/msdeploy.axd?site=my site name'. Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond myip.com
Any help will really be appriciated
The real error message is buried in the report, but it reads:
"Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond myip.com"
This is a TCP connection problem, which means there's probably a simple solution.
It should be straightforward: it means the server you've specified is not operational. If you're certain that your website is currently working (i.e. you can get to it from your web-browser) then it means you've mistyped the server's name or other connection details. It does not mean that msdeploy.axd is having problems because if it were, your client would at least be able to connect.
Check your server's firewall rules, and also ensure that the web server (IIS) is running and is actively listening on the IP address you want (check the site bindings and also the server's network configuration, a dump of ipconfig /all would also be useful).
It was the issue with IIS it was not allowing remote connections. fixed it by allowing remote connections.
In my case it was due to the firewall setting of the host machine. Turning off firewall for local network fixed the problem