Ramon said:
I've tested the client program on Linux and it worked perfectly
(compiler version 1.6.0_07) -- i.e. when there was no server running on
port 60000, the client had thrown java.net.ConnectException.
It means that either:
[1] There is a bug in Windows (for a change
)
Unlikely, but not impossible. Noone else with Windows has been able to replicate
your problem so it's unlikely to be a simple problem. But there could be some
special configuration setup in your system which has triggered this problem.
[2] or my Windows javac is "corrupted"
I don't see how the compiler could be at fault. That only converts your Java
source code to byte-code. The actual Socket code is in rt.jar, which is
presumably downloaded from java.sun and is exactly the same code everyone else
is using.
[3] or, as some of you has pointed out, their might be some sort of
program running in the background...etc.
That seems most likely. If you had a firewall previously check it has been
removed from the system entirely, it might not have uninstalled completely if
it was active when you uninstalled it. Check that the Windows firewall is
really disabled - Windows has nasty habit of ignoring what you tell it do do
and doing what it thinks best instead. Check your AV to see if it monitors
incoming network connections- I believe some monitor network traffic for
virus/trojan payloads. Try a different port - is this specific to port 60000?
