For testing purposes, I'm trying to run a number of client applications connecting to a server all on the same host machine.
The host machine is running Windows 2008 Server Standard 32-bit with Service Pack 2.
On my XP development machine I installed the Microsoft Loopback Adapter in order to run multiple clients connecting from separate IP addresses. My LAN network is 192.168.1.xxx and so I chose 192.168.5.xxx for the loopback adapter addresses.
On my development machine, everything works fine and I am able to see the client applications binding to the loopback adapter using TCPView.
When I try and run the same setup on the Windows 2008 server with the same settings, the client applications are unable to bind to the loopback adapter addresses. There is no activity in TCPView and so I believe there's possibly some configuration setting I'm missing in setting up the loopback adapter.
Can anyone help?
Thanks!
Nick.
Ok, problem solved. I was specifying that the client connect to 127.0.0.1 but when I asked it to connect to a 192.168.5.x address it worked. The server was bound to 0.0.0.0 which suggests that it should still have been bound to 127.0.0.1 anyway but it just didn't seem to work!
Related
I have a Django project running with Nginx and Waitress on my Windows VPS. I want to make it accessible to the public with a domain name. I am completely clueless on how to go about it, although I have pointed my domain's A record to the Public IP address of the VPS. To be specific, I am running a Windows Server 2019 on the Gcloud platform.
Check and make sure your VPS firewall settings are such that it allows request from public site at Port 80.
I just found a way to do it. I edited my Windows Server 2019 VPS firewall and added a port inbound rule, enabling request from remote clients on port 80 which is the port my nginx server serves from. #AnirudhBargi i guess i didn't understand your initial question. Enabling port 80 to accept request was the solution all along. Thank you very much.
I am toothily new to server side and I want host a web service in my newly created windows server 2008 r2 virtual machine. however i cannot get it up there. I am getting errors after such as MIME type, sometimes files get downloaded, Permission errors, protocol mapping.
Therefore, I would like to know how to host a WCf Application from the begining. Thanks in advance
Here are excellent guides you can refer to host a WCF service in Windows Server 2008 R2:
http://broomandan.blogspot.in/2011/04/how-to-configure-windows-server-2008-to.html
http://blogs.technet.com/b/meamcs/archive/2014/02/16/wcf-service-manual-deployment-on-windows-server-2008-r2.aspx
I am using Macbook air and its OS is OS X 10.8.5, installed win7 with virtual box.
And developing web application at win7 virtual box, I want to port forward virtualbox
port to host port. So that I could test app on the host and also to the mobile phone
using same wifi.
First I didn't type host and guest ip and put the port value 8000.
I figured out guest ip and host ip by writing "ipconfig" and "ifconfig".
After running server of guest, I wrote the web address on host browser like below,
http://[guest ip]:8000/
But cannot load the web page of guest.
What is the problem?
And also if I want to load the web application of virtualbox to mobile phone
How could I do it?
Though it looks a bit silly, It would be glad to have an advice.
Thanks in advance :)
I would not recommend you to work that way, you can develop your web application right in your OSX, it would be much easier.
But if you have to do that way. Then first, because your network configuration is NAT, your VM will has an private IP like: 10.0.2.15, you need to forward to port to access, it likes:
From the above image, I forward port 2022 to 22, 2080 to 80 (web server)
So let's say your web is running at the same port 80, here is the URL for you to access to your web: 127.0.0.1:2080
BTW for me i don't like to work through the port forwarding, I prefer to configure my VM using "host only". By that way you can have an ip like 192.168.x.x and you can forget the port forwarding. You can read it more from here:
https://www.virtualbox.org/manual/ch06.html#network_hostonly
Hope it helps you.
I have coded a web service using the Axis 2 framework and I can successfully invoke it using a test client (SoapUI) on the local machine after publishing the application in JBoss 5. I can post to the WS endpoint from the local machine and get the expected response.
Now i want to allow other machines to access the web service.
i changed the "localhost" to "my own fixed IP" adress at the end point location, and turned firewall off, but impossible to access the WS.
Note : windows Xp SP3.
Any idea ?
Thanks in advance !!
Please ensure you follow below steps
For example, if your ip is 10.132.243.54
List item
Checking if your IP is pingable by other systems
Instead of running with eclipse, run your jboss from your
command-prompt
start jboss-server suffixing -b in run.bat. The command is run.bat
-b 10.132.243.54
Access the WS from SOAP-UI using IP and not using localhost
If your IP is still not pingable, turn off the firewall, after
following above steps
Sorry for the late reply, However this would solve the problem i guess
I have a Javax web service deployed in a remote Linux machine within a JBoss ESB container. I am able to test the web service using soapUI on the same machine as where the service is deployed. The WDSL URI I used was something like http://127.0.0.1:8080/abcd/abcd?wsdl.
What I would like to do is to be able to test the same service from another machine using soapUI. I tried replacing 127.0.0.1 with the IP address of the machine where the service is deployed. This does not seem to work. Can someone tell me what I am missing here?
Thanks.
a sum of things could go wrong there - as already mentioned by the others the firewall is blocking access for the given (address, port) pair. Another thing that happened to me was that the WSDL was generated using the name of the machine it was deployed on and whenever I was trying to call the service from a different machine it was complaining that I cannot find the given machine.
You need to test network connectively. One tool you can use is plain old telnet. If you telnet to the ip/port combo of the web server, you will get a response (an HTTP error). For example:
$ telnet 192.168.0.10 8080
If you get nothing then there is almost certainly a firewall blocking access.
If you are convinced that no firewall is blocking you, the other possibility is that the web server is only bound to the local network adapter (127.0.0.1) and not the other network adapters (ethernet/wifi). This is very unlikely however.