Click to See Complete Forum and Search --> : [RESOLVED] Router problems


grahamr (work)
October 27th, 2006, 08:03 AM
I have a program that uses a mini webserver running on port 90 and an app that runs on port 1200. The app listening to port 1200 is started by the webserver and is designed to listen to incoming requests from a activex application. It is currently being debugged on my machine.

Both programs work when ran on a LAN. The program also works when running via a Dialled in connection direct to my machine (via a laptop). Using VNC to connect to my colleagues home machine and from there connect to the works machine works for the webserver but when the webserver returns the activex control embedded in the page it (the control) fails to connect to the app on port 1200.

The page has the IP and port number that it needs to connect to as parameters for the object (the page is created dynamically as users connect) and the dataserver knows where to listen for connections from. However the app returns a 10060 error message (Timeout error) on the connect() function.

You may think that I am using an internal address (192.168.etc) but I am currently hardcoding the office IP address as seen from the outside world while I research a better solution. My best idea is to have a secret page on the office website that will return the accessing IP so the webserver will know what the dataserver's forward facing IP will be.

So I am thinking it must be due to routing issues. However the 90 is forwarded correctly to my machine via Port Forwarding on the company router and the 1200 has the same settings attached to it.

Anybody have any ideas that might be causing the problem?

grahamr (work)
October 27th, 2006, 10:06 AM
Update: Changed the port to 91 and it now works. Something wasn't liked about port 1200...

1200 was just plucked out the air...