We ran into this problem yesterday where a customer went from Windows Vista 64-bit to a new computer running Windows 7 64-bit. The registry fix Kim supplied below fixed the problem. Thanks Kim!
(Interesting note to this- our customer had been using Windows Vista 64-bit for well over a month with no issues, so I wonder what the configuration value is that is causing this to happen? We're not able to do a detailed config review of the user's workstation unfortunately...)
Of course, the customer later went ahead and applied updates from Microsoft and the problem reoccurred- apparently Microsoft is doing SOMETHING with port 1099. Reapplying the registry fix solved the problem once again.
To work around this I think we might just push all of our application servers to run through port 443 as I really don't want to get into this issue repeatedly with our customers- I'd rather avoid the whole issue of trying to find relatively available ports that won't get co-opted later by Microsoft somehow.
Anyone else run into this with the launch of Windows 7?
-Tony
kwpsd wrote: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