fsc Could not connect to compilation daemon

[scabug]

fsc command in a command prompt produces this message.
scala and scalac work.
I set SCALA_HOME, JAVA_HOME, and added scala bin to a path in system properties and verified in using set command.
I also tried setting the same in a command prompt - fsc produces the same message.
The same scala version works on a different computer, also Win XP.

I use version 2.7.7 on Windows with Sun JDK 1.6.0_17.

Because of this problem, Netbeans plugin does not work.

Eclipse plugin works, though.

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-2584?orig=1
Reporter: Alex (air77)

[scabug]

@adriaanm said:
This should be fixed in 2.8. Could you please try with a nightly build?

[scabug]

Alex (air77) said:
C:\lang\scala\2.8.nightly>set S
SCALA_HOME=C:\lang\scala\2.8.nightly

C:\lang\scala\2.8.nightly>bin\fsc.bat
Could not connect to compilation daemon.

C:\lang\scala\2.8.nightly>bin\fsc.bat -verbose
[Server arguments: -d C:\lang\scala\2.8.nightly. -verbose]
[VM arguments: ]
[Temp directory: Directory(C:\DOCUME1\alex\LOCALS1\Temp\scala-devel\alex)]
[Executed command: C:\lang\scala\281FFA~1.NIG\bin..\bin\scala.bat scala.tools.nsc.CompileServer]
[Port number: -1]
Could not connect to compilation daemon.

C:\lang\scala\2.8.nightly>

I used

http://www.scala-lang.org/archives/downloads/distrib/files/nightly/distributions/scala-2.8.0.latest.zip

[scabug]

@adriaanm said:
Toni, could you have a look?

[scabug]

@cunei said:
Hello, I tried a recent 2.8.0 nightly with Sun JVM 1.6.0_15, and all works here; that was without setting SCALA_HOME. We have not received any other reports of difficulties with fsc on Windows.

Fsc relies on the ability to establish a network connection with the local machine: it first starts a compilation server, which is left running in the background, and then it contacts that server via a socket connection with every new invocation of fsc. If you have a particularly strict firewall software installed on your machine, that may prevent fsc from contacting its own daemon.

If you are still experiencing this problem, you might try to adapt the firewall configuration so to allow local connections, or temporarily switching it off and try again. We are unable to reproduce this problem here, therefore we will close the ticket for the moment. Please reopen if you still encounter this issue.