X-Win32 Knowledge Base   >   Cannot Connect to a Host on a Restricted Network

Search


About StarNet

StarNet Communications has been a leading developer of X Windows solutions since 1989. After establishing X-Win32 as the de facto standard in the higher education market during the early to mid-1990s -- 150 unlimited Campus Site Licenses worldwide -- X-Win32 has become of one the top three PC X servers in the government and commercial sectors as well.

Unlike its major rivals, Exceed (Hummingbird) and Reflection-X (WRQ/Attachmate), X-Win32 offers a highly focused PC X server that offers superior performance and productivity features, stability, ease of use and low cost (40% or better in most cases).

StarNet also delivers unequaled customer support. Our state-of-the-art engineering infrastructure allows us to fix problems and make a new release available quickly (overnight in many cases). As our testimonials page shows, StarNet customers consistently rate their X-Win32 experience as the best in the industry.




Cannot Connect to a Host on a Restricted Network

You will receive a Connection refused by Server: Cannot connect to host on a restricted network message if the license you have is restricted to a certain subnet and you are trying to connect to a host on a different subnet.

There are several possible solutions to this message.

1. Put the computer you would like to connect to on one of the subnets which your license has the ability to access.

2. Get a Node locked license. Node locked licenses do not have any subnet restriction. You can request a node locked license from the system administrator who gave you the original floating license.

3. Contact the system administrator who gave you the floating license and request that he add the subnet you are currently on to the floating license key. Note that subnets will only be added if your company’s current point of contact with StarNet makes this subnet request.

Category:Licensing
Category:Licensing -> Floating