Main Area and Open Discussion > General Software Discussion

How to determine ipaddress of mini-webserver on a wireless network

(1/3) > >>

patteo:
I'm testing a software application that also runs a mini-webserver so that it's database can be accessed from the web via port 82.

I made sure that my firewall, I allowed Incoming TCP ports 82 and allowed Outgoing TCP ports 82.

There's one thing that I'm rather confused by.

If I use Windows ipconfig command, I can see my address as 192.168.1.100 (on computer A where the mini-webserver resides)

And if I use http://192.168.1.100:82 I can actually see the data on the mini-webserver, but it is only accessing Computer "A" locally via my wireless network.

If I use a tool like FollowmeIPlite (http://www.snapfiles.com/Freeware/network/fwip.html), my External IP address is shown as 202.156.173.124 for example.

Now I have 3 computers A, B, C in my home network. Each one of them show exactly the same External IP address 202.156.173.124

But computer "A" is where the mini-webserver resides.

If windows ipconfig command shows :
"A"  ipaddress as 192.168.1.100
"B"  ipaddress as 192.168.1.101
"C"  ipaddress as 192.168.1.102

What would be the correct url to put in a browser for me to access port 82 on computer "A" from anywhere on the internet ?

http://202.156.173.124:82          - This would be incorrect as which of the computers would it refer to since A, B, C has the same External IP address. In fact the browser cannot locate the mini -webserver at all.

http://192.168.1.100:82             - This would be incorrect although it would access the data via the internal network which is not what I want.

So the url is somehow a combination of both.

Is there some software utility that can help me determine the correct answer ?

I would appreciate if someone can point me to a solution ? Thanks

patthecat:
The main thing you need to do is called port forwarding from your router on port 82 to a specific computer where your mini webserver is.

Look at the following site: http://www.portforward.com
This shows you how to do it for common routers.

It basically involves going into the router settings and telling it that any incoming requests from the internet on a specific port get redirected to a specific local ip address. In your example, people would refer to your web server as {external ip address}:82
Your router sees that port 82 was requested so it forwards the info to the mapped local ip address 192.168.1.100 where your web server resides.

patthecat:
Also I don't think you need the firewall setting of outgoing TCP port 82 enabled since web server basically would use port 80 automatically by default which you would have open usually. 

The way I see it, incoming request need to specify the port number since it needs to go to the web server.  But a response to the request can go on port 80 (I think).

Once you have port forwarding enabled see if the "outside" users can connect without the firewall outgoing port 82 configured.

patteo:
Thanks patthecat for the suggestions on Port forwarding and closing of TCP outgoing.

I tried it and it works.

The only thing is that my Linksys WRT54G dynamically assigns the ip addresses and sometimes I find Computer "A" is assigned 192.168.1.100 and sometimes, after a reboot it is assigned 192.168.1.101.

How does one stop this dynamic assignment.

I was looking through the settings and cannot seem to figure out how to assign static addresses like 192.168.1.100 to say Computer "A".

Any suggestions ?

Thanks again.

jgpaiva:
patteo: you need to disable DHCP (which is what assigns those ips) and configure static ips on the computers, one per computer.

Navigation

[0] Message Index

[#] Next page