by kwpsd » Tue Feb 17, 2009 9:59 pm
We installed Servoy on a new Windows Vista 64-bit computer (to act as a Servoy server) and ended up with a myriad of problems...this being one of them!
Using the 'netstat -a' command, we found that Sybase SQL port 2638 and Servoy Server port 8080 were open and LISTENING, however, the RMI port 1099 didn't show up. Using the 'telnet' command to port 1099 resulted in a message stating that a connection could not be established. Conflicting information at best..here's why.
A failure to 'telnet' to port 1099 indicates that some other application/service/system thing is already using the port, but, if that is true, then you would expect to see port 1099 to appear in 'netstat -a' as LISTENING. Microsoft at its best, eh? The conclusion we made was that Windows Vista is (secretly) using port 1099 even though it's a reserved port for Java RMI.
So, how to get around this? We added the following key to the Window Registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Create a new multi-string value key (REG_MULTI_SZ) in this location and name it 'Reserved'. For the range value, enter '1099-1099'. Save and close the registry editor, then re-start the computer.
Disclaimer: we do not know what the ramifications to Windows Vista are, if any, for reserving port 1099. If you know of any, please let us know.
I hope this helps!
Kim
Kim W. Premuda
San Diego, CA USA