And after all that, if I delete the domain, I can't re-register it, because:

Unsupported domain at C:\...; Admin-listener is disabled or no enabled http-listener

Please, attach your messages log (View|IDE Log) from time when it is not possible to start GlassFish domain. Or try to create a new domain in some area without windows access restrictions.

I have all access rights on the folder I put domains into

Here is what is written to the IDE log after I try to start the server:

INFO [org.glassfish.tools.ide]: [GlassFish Server 3+] Port check could not connect to localhost:4848: Connection refused: connect
INFO [org.glassfish.tools.ide]: [GlassFish Server 3+] Port check could not connect to localhost:4848: Connection refused: connect

What version of GlassFish did you use?

Looks like NetBeans can't connect to 127.0.0.1:4848 after server is started.
Check your windows if there is something blocking access to this IP:port. Also try if you can access it from web browser (guess you don't have telnet to try just plain network connection).

As another step to get more information, put -J-Dglassfish.level=0 -J-Dorg.glassfish.tools.ide.level=0 options into netbeans_default_options in your netbeans config file (etc/netbeans.conf) and reproduce this issue again. It will produce more detailed log about server startup.

Attach it to this bug.

I doubt something is blocking the port. Domain starts just fine. And stopes. And starts again. And starts after I reboot the computer, and so on. Domain administrator console works good. 

Then I deploy "Hello, world!" web app. It's done just fine as well. Then I start the app and it works. But if I stop the domain, It won't be started again if I try to start it as one embedded into NetBeans. 

But still can start it with asadmin, deploy applications, use administrator console and so on

Created attachment 135119 [details]
What happens when I start NetBeans and try to start GlassFish

"-J-Dglassfish.level=0 -J-Dorg.glassfish.tools.ide.level=0" was added to netbeans_default_options as Tomas suggested

GlassFish is 3.1.2.2 (build 5)

Problem seems to be in failing port check. Unfortunately I can't do much with this. It's just simple
            InetSocketAddress sa = new InetSocketAddress(host, port);
            Socket socket = new Socket();
check to see if something is listening on IP:port of admin interface.

In 7.3.1 this check provides more details about exception thrown in those 2 lines of code.

Try to download http://bertram2.netbeans.org:8080/job/javaee7/lastSuccessfulBuild/artifact/nbbuild/NetBeans-dev-javaee7-332-on-20130529-full.zip and see if it works for you. If not, just add the same debug options into it's config file and attach logs again.

Created attachment 135142 [details]
What happens when I start NetBeans and try to start the server

GlassFish is 4.0 (build 89)

This time I performed the experiments in Windows 7 (64)

Still NetBeans can't do what asadmin can

Created attachment 135146 [details]
netstat -a -b when NetBeans is waiting for GlassFish to start (but it won't)

No 4848

Could it be NetBeans itself that prevents it from listening to the port? Because realy (sorry for repeating) probability that it's some other process realy seems pretty low to me

Why that other process does not interfere before I deploy something?

How such an internal to NetBeans and GlassFish thing as deployment of an app can force some other process to start making problems (and continue after reboot of the OS)?

Why it doesn't make a problem for GlassFish network server, so the domain can be started with asadmin?

Why after all "netstat -a -b" can't see that process?

And why deployment make the domain go "Unsupported domain at C:\...; Admin-listener is disabled or no enabled
http-listener"?

Well, I simply don't know. I need to get full logs of server startup with -J-Dglassfish.level=0 -J-Dorg.glassfish.tools.ide.level=0, not just small pieces.
I don't see server startup command and following status checks there.

Created attachment 135273 [details]
Take two

Actions are:
1. IDE startup
2. Expanding "Services/Servers" node
3. Starting the GF (sucessfuly, because no app has been deployed yet)
4. Deployment of the "Hello World!" application
5. Stopping the GF
6. Attempt to start the GF again (fails)

I've commented the places in the log file where each action starts

^^ that is an IDE log file

Created attachment 135277 [details]
IDE log file, take #3

Actions are:
1. IDE startup
2. Expanding "Services/Servers" node
3. Starting the GF (sucessfuly, because no app has been deployed yet)
4. Deployment of the "Hello World!" application
5. Stopping the GF
6. Attempt to start the GF again (fails)

I've commented the places in the log file where each action starts

This looks really bad.
Well, in the logs you can find command line arguments that are executed:

FINEST [org.glassfish.tools.ide]: Java VM D:\glassfish3\jdk7\bin\java.exe executable version 1.7.0_11

FINEST [org.glassfish.tools.ide]: Starting GlassFish Server 4.0 (domain 6) using Java VM D:\glassfish3\jdk7\bin\java.exe and arguments -cp "D:\Program Files\glassfish-4.0\glassfish\modules\glassfish.jar"  -XX:MaxPermSize=192m -client -Djava.awt.headless=true -Djavax.management.builder.initial=com.sun.enterprise.v3.admin.AppServerMBeanServerBuilder -XX:+UnlockDiagnosticVMOptions -Djava.endorsed.dirs="D:\Program Files\glassfish-4.0\glassfish/modules/endorsed;D:\Program Files\glassfish-4.0\glassfish/lib/endorsed" -Djava.security.policy="D:\Program Files\glassfish-4.0\glassfish\domains\domain6/config/server.policy" -Djava.security.auth.login.config="D:\Program Files\glassfish-4.0\glassfish\domains\domain6/config/login.conf" -Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as -Xmx512m -Djavax.net.ssl.keyStore="D:\Program Files\glassfish-4.0\glassfish\domains\domain6/config/keystore.jks" -Djavax.net.ssl.trustStore="D:\Program Files\glassfish-4.0\glassfish\domains\domain6/config/cacerts.jks" -Djava.ext.dirs="D:\glassfish3\jdk7/lib/ext;D:\glassfish3\jdk7/jre/lib/ext;D:\Program Files\glassfish-4.0\glassfish\domains\domain6/lib/ext" -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver -DANTLR_USE_DIRECT_CLASS_LOADING=true -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory -Dorg.glassfish.additionalOSGiBundlesToStart=org.apache.felix.shell,org.apache.felix.gogo.runtime,org.apache.felix.gogo.shell,org.apache.felix.gogo.command,org.apache.felix.shell.remote,org.apache.felix.fileinstall -Dosgi.shell.telnet.port=6666 -Dosgi.shell.telnet.maxconn=1 -Dosgi.shell.telnet.ip=127.0.0.1 -Dgosh.args=--nointeractive -Dfelix.fileinstall.dir="D:\Program Files\glassfish-4.0\glassfish/modules/autostart/" -Dfelix.fileinstall.poll=5000 -Dfelix.fileinstall.log.level=2 -Dfelix.fileinstall.bundles.new.start=true -Dfelix.fileinstall.bundles.startTransient=true -Dfelix.fileinstall.disableConfigSave=false -XX:NewRatio=2 -javaagent:"D:\Program Files\glassfish-4.0\glassfish\lib\monitor\flashlight-agent.jar" -D"com.sun.aas.javaRoot=D:\glassfish3\jdk7" -D"com.sun.aas.derbyRoot=D:\Program Files\glassfish-4.0\javadb" -D"com.sun.aas.instanceRoot=D:\Program Files\glassfish-4.0\glassfish\domains\domain6" -D"com.sun.aas.installRoot=D:\Program Files\glassfish-4.0\glassfish" com.sun.enterprise.glassfish.bootstrap.ASMain --domain domain6 --domaindir "D:\Program Files\glassfish-4.0\glassfish\domains\domain6"

FINEST [org.glassfish.tools.ide]: Setting GlassFish Server 4.0 (domain 6) process current directory to D:\Program Files\glassfish-4.0\glassfish\domains\domain6

Try to run this manually to see what will happen. Just copy paste
D:\glassfish3\jdk7\bin\java.exe and everything following -cp  and check what will happen. There may be something wrong - e.g. missing "" around path containing space or wrong order of arguments.

Please can you try to reproduce this with NetBeans 7.3.1 and also latest development build of NetBeans 7.4?

I would like to know if 7.3.1/7.4 are able to detect server status. There were some significant changes in server state monitoring, especially in 7.4.

Do it with -J-Dglassfish.level=0 -J-Dorg.glassfish.tools.ide.level=0 to see extended debug info for the plugin.

Also I remember that we fixed server status checks in 7.3 before release where there was typo which was causing exactly the same problem. And after that this kind of bug was never reported again.

So this is a duplicate of Bug# 221075. I should have asked you to reproduce this with some newer version immediately.

If you see the same problem with 7.3.1 or 7.4 dev build feel free to reopen this bug again.

*** This bug has been marked as a duplicate of bug 221075 ***