port out of range

[vinograd]

Hi,
I have been using Wingate 6.6 on a Windows XP machine for several years. The HTTP service was configured to allow a couple of computers on the internet (belonging to my collaborators), defined by their location (IP addresses), to access this service. A few days ago I migrated the server onto a newer Windows 7 (32-bit, SP 1) machine. I configured everything in exactly the same way as before, it seems, and everything is working nicely... except that these outside computers cannot access the HTTP service anymore. I can see them trying reach the right interface and connect via the right port (80), but Wingate rejects them saying 'Port out of range'. The number shown near that message in the Firewall tab is obscure, some 53587 or something like that. (I suppose these are the port numbers on these remote computers?? - I am not sure). As i said, the rights to use the HTTP service are configured to be defined by location, and the IP addresses of the computers of my colleagues are explicitly entered into the configuration. Also, the bindings of the service are configured such that the requests to use the service are accepted on the internet (extrenal network) adapter interface. Nevertheless, Wingate rejects them. Does anyone know what might be wrong?
Thank you!

[adrien]

Hi

so you reinstalled WinGate 6.6.4 again, or did you also update WinGate to a later version?

"Port out of range" is not an error that WinGate generates itself, where do you see that error? E.g.

* in the client browser
* in some WinGate logs or activity screen

You see the activity in WinGate when the clients connect?

Is this piping through to a back end web server (e.g. reverse proxy) or is WinGate acting as the http server itself? If so is it using CGI?

Regards

Adrien de Croy

[vinograd]

Thanks, Adrien. First of all, I am sorry, misspoke. There is no error 'port out of range' generated per se, but in the Firewall tab where it shows a red crossed circle, the Reason for service denial is listed as Port Range. Secondly, yes, it is the same old Wingate 6.6. And lastly, I think that I may have solved the problem accidentally - not sure, as no one tried to connect yet. There are two panels in the HTTP Service configuration-Bindings. The one at the top shows actual bindings, I think, whereas the one at the bottom shows binding policies. I am not exactly sure why and how a connection can appear in Binding Policies, but not in Bindings, but this is what actually happened. I enabled binding, through a pop-up menu, to my external adapter 'only', and it appeared in the bottom panel. However, nothing changed in the upper panel until I enabled binding to ALL external interfaces. After I did that, my external adapter shows in the upper panel, and I think everything should be working. I did make sure tough through the Policies menu that the Default Policies are ignored, and service is granted by location. I hope it solved the problem... but if not, i'll be back. Thanks again!

[adrien]

Hi

ok thanks you should probably check adapter usage setting in the network connections panel, if your external adapter is set to internal that could explain it.

Regards

Adrien