Hi,

I am trying to host my application using Web Server Pro and everything works perfectly when I am accessing it from the local system. But the network access does not work. I tried to use IP address and computer name, but was not able to access the application.

Could you please suggest how can I debug this issue, to find the root cause?

Thanks!

Thanks, will try it.

Looks like a firewall issue - by disabling Windows Firewall on the system where server is installed (Windows 7) I can resolve it. Is it expected that the users need to modify Firewall setting before hosting the network facing sites?

Hi I am using build 14 and I have the same problem in Vista 32-bit and Windows 7 64-bit.

Initially I added exception to the following programs (UDP and TCP, Public and Private profile) but I can't still access my web app from LAN:
c:\program files (x86)\UltiDev\Web Server\UWS.AppHost.Clr4.x86.exe
c:\program files (x86)\UltiDev\Web Server\UWS.AppHost.Clr4.AnyCPU.exe
c:\program files (x86)\UltiDev\Web Server\UWS.AppHost.Clr2.x86.exe
c:\program files (x86)\UltiDev\Web Server\UWS.AppHost.Clr2.AnyCPU.exe

My web app is hosted using port 81. When I run this command (in Vista and 7 64-bit): netstat -ao | find "LISTENING"
It shows that 0.0.0.0:81 and [::]:81 is hosted by process id 4, which is "System".

So I had to add "Inbound Rules" for port 81 in Windows Firewall, then I can access the web app from LAN.
Is that the correct way?

Thank you very much.

I think I found the problem.

UWS adds the port rule but only to the "Private" profile.
If I tick "Domain" and "Public" (under "Advanced" tab of "UltiDev Web Server Pro" rule properties), then I can access from LAN.

The scope (under 'Scope' tab) may also cause problem since the "Remote IP address" is set to "Local subnet" only. IP outside the LAN may not be able to access web apps.

Hi,

Our application are meant to be accessed from internet, so we need the rules to be set in "All profiles" and "Remote IP address" to be "Any IP address".
UWS server <---> Internet <---> clients


However, here's my current development environment (all on the same subnet):
-Clients joins a domain
-UWS are installed in machines that join the same domain.
-UWS are also installed in virtual machines (to test against various OS), which are on the same subnet but does not join the domain.

Clients cannot access UWS (both real or virtual machines) unless "Public" profile is ticked in the firewall rule. Ticking "Domain" profile does not work.

Thanks. Here's what I found after some testing:

I guess UWS add firewall rules using current network profile, as shown in Network and Sharing Center. Eg, if the current profile is Private, rules will be added to Private profile.

My development machine has a real network interface (Domain network) and a virtual network interface (Private network).
If I disable the virtual network interface, UWS will add rules to Domain profile. Clients can access UWS in this scenario.
If I enable the virtual network interface, UWS will add rules to Private profile. Clients cannot access UWS in this scenario, unless I tick 'Public' in the rule. I don't know why but 'Private' and 'Domain' just don't work, maybe this is a bug in Windows Firewall.

Would it be better if UWS just add rules to 'All profiles'? Users may change profile without UWS knowing it.


Another thing is, UWS only create firewall rules when I click "Save config changes" in UWS Explorer. It does not add rules when Metabase.RegisterApplication() is called in a program.

Thanks! Guess I will have to add the rule myself.

Metabase.RegisterApplication() is run under a separate application which requires elevated account.

Hi, Metabase.RegisterApplication() does create the rule when running under elevated account. The problem is, as you said for security reason, it won't create to Public profile even though the current network is public. So my solution is to make my application create another rule to Public.