I don't know any reason why if this worked before it shouldn't still work with 4.2.3. By default 4.2.3 binds sockets to localhost if you don't pass a -b value to run.bat. But you say you can access the node via http://1.1.1.1:8080 so that doesn't sound like the problem.

4.0.3 would bind to all interfaces, localhost included, if you didn't use -b. Binding to all interfaces by default wasn't secure.

Try this:

run -b 0.0.0.0

which will bind to all interfaces. If you are using the "all" config that could lead to issues though, which we can get into if the above helps.

I don't use Windows NLB so I can't comment on config details, beyond saying there's nothing in the AS configuration specifically oriented toward integrating with it.

Good; glad you are making progress.

If you are running with the all config, use this:

run -c all -b 0.0.0.0 -Djgroups.bind_addr=1.1.1.1 (or 2.2.2.2)

JGroups will ignore 0.0.0.0 and pick an interface; using -Djgroups.bind_addr=1.1.1.1 lets you specify which.

Also, clustering's HAPartition service uses the -b value plus the JNDI port (1099 by default) to make up a unique id for each node. If you use -b 0.0.0.0 (or -b 127.0.0.1) each node will come up w/ the same name -- not unique, which may lead to problems. To work around this you can manually specify the name by editing the cluster-service.xml file, replacing:

<attribute name="NodeAddress">${jboss.bind.address}</attribute>

<attribute name="NodeAddress">${jgroups.bind_addr}</attribute>