Selenium Grid2 Node Registration Fails

[CuriousTester]

Hi All,

I'm failing to register node on grid using latest Selenium server
version 2.22.0 on the same machine on which hub is running. Following
message is recieved -

14:33:38.703 INFO - couldn't register this node : Error sending the
registration
request.
14:33:43.711 INFO - couldn't register this node : hub down or not
responding.

Here are the commands used -

To register server -
java -jar selenium-server-standalone-2.22.0.jar -hub

To register node
java -jar selenium-server-standalone-2.22.0.jar -role wd -hub http:/
/localhost:4444/grid/register

Note that I`ve checked server is up and running on browser.

I could not find much help on this earlier posts so any help is
appreciated

Thanks!

[Ankit]

You're supplying the wrong command line arguments for the hub. To
start the hub, use:

java -jar selenium-server-standalone-2.22.0.jar -role hub

Check out the wiki page, it explains all of this:
http://code.google.com/p/selenium/wiki/Grid2

> --
> You received this message because you are subscribed to the Google Groups "Selenium Users" group.
> To post to this group, send email to seleniu...@googlegroups.com.
> To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
>

[pravi...@gmail.com]

Ankit,

I've no problems starting the hub. I'm having issue to register the node.

Command I posted is from Documentation section on Selenium website & is correct.

Thanks for reply & still looking for solution.

Sent from my BlackBerry device on the Rogers Wireless Network

[Naresh Thandu]

Hi,
I think you can try these

java -jar selenium-server-standalone-2.22.0.jar -role hub http://10.10.5.45:5555/grid/register

java -jar selenium-server-standalone-2.22.0.jar -role node -hub http://10.10.5.45:4444/grid/register -maxSession 10 -browser browserName=firefox,maxInstances=10

Thanks,
Naresh

Regards,
Naresh Thandu,
+91-9916710222

[CuriousTester]

Hey Naresh,

Thanks for suggestion!

Though, commands mentioned in your reply are mixed up, I believe you
are referrring to try regsitering hub & node with IP address of
machine. I had tried this earlier with no luck.

Support from any senior group members or developers is appreciated.

Thanks!

On Jun 2, 3:53 pm, Naresh Thandu <naresh.tha...@gmail.com> wrote:
> Hi,
> I think you can try these
>

> java -jar selenium-server-standalone-2.22.0.jar -role hubhttp://10.10.5.45:5555/grid/register
>
> java -jar selenium-server-standalone-2.22.0.jar -role node -hubhttp://10.10.5.45:4444/grid/register-maxSession 10 -browser

> browserName=firefox,maxInstances=10
>
> Thanks,
> Naresh
>
>
>
>
>
> On Sat, Jun 2, 2012 at 2:40 AM, <pravirjo...@gmail.com> wrote:
> > Ankit,
>
> > I've no problems starting the hub. I'm having issue to register the node.
>
> > Command I posted is from Documentation section on Selenium website & is
> > correct.
>
> > Thanks  for reply & still looking for solution.
>
> > Sent from my BlackBerry device on the Rogers Wireless Network
>
> > -----Original Message-----
> > From: Ankit <ankitso...@gmail.com>
> > Sender: seleniu...@googlegroups.com
> > Date: Fri, 1 Jun 2012 16:57:16
> > To: <seleniu...@googlegroups.com>
> > Reply-To: seleniu...@googlegroups.com
> > Subject: Re: [selenium-users] Selenium Grid2 Node Registration Fails
>
> > You're supplying the wrong command line arguments for the hub. To
> > start the hub, use:
>
> > java -jar selenium-server-standalone-2.22.0.jar -role hub
>
> > Check out the wiki page, it explains all of this:
> >http://code.google.com/p/selenium/wiki/Grid2
>

> > On Fri, Jun 1, 2012 at 2:49 PM, CuriousTester <pravirjo...@gmail.com>

[CuriousTester]

After failed registration of node, when command is terminated, I
noticed that IP address reported is 0.0.0.0:4444

Here are the commands used

Hub Startup
java -jar selenium-server-standalone-2.22.0.jar -hub
http://10.242.70.127:4444/grid/register

Node Registration

java -jar selenium-server-standalone-2.22.0.jar -role node -hub

http://10.242.70.127:4444/grid/register -port 5555 -maxSession 10 -
browser browserName=firefox,maxInstances=10


Output on hub console on loading console page in browser
11:52:58.808 INFO - Started SocketListener on 0.0.0.0:4444

Output on node console on terminating the command on failed
registration -
12:32:58.863 INFO - Stopping Acceptor
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=5555]

Have spent quite bit of time on this with no avail so would be great
if anyone can advise where this situation was faced.

Thanks!

On Jun 4, 12:10 pm, CuriousTester <pravirjo...@gmail.com> wrote:
> Hey Naresh,
>
> Thanks for suggestion!
>
> Though, commands mentioned in your reply are mixed up, I believe you
> are referrring to try regsitering hub & node with IP address of
> machine. I had tried this earlier with no luck.
>
> Support from any senior group members or developers is appreciated.
>
> Thanks!
>
> On Jun 2, 3:53 pm, Naresh Thandu <naresh.tha...@gmail.com> wrote:
>
>
>
> > Hi,
> > I think you can try these
>
> > java -jar selenium-server-standalone-2.22.0.jar -role hubhttp://10.10.5.45:5555/grid/register
>

> > java -jar selenium-server-standalone-2.22.0.jar -role node -hubhttp://10.10.5.45:4444/grid/register-maxSession10 -browser

> > browserName=firefox,maxInstances=10
>
> > Thanks,
> > Naresh
>
> > On Sat, Jun 2, 2012 at 2:40 AM, <pravirjo...@gmail.com> wrote:
> > > Ankit,
>

> > > I've no problems starting the hub. I'm having issue toregisterthe node.

>
> > > Command I posted is from Documentation section on Selenium website & is
> > > correct.
>
> > > Thanks  for reply & still looking for solution.
>
> > > Sent from my BlackBerry device on the Rogers Wireless Network
>
> > > -----Original Message-----
> > > From: Ankit <ankitso...@gmail.com>
> > > Sender: seleniu...@googlegroups.com
> > > Date: Fri, 1 Jun 2012 16:57:16
> > > To: <seleniu...@googlegroups.com>
> > > Reply-To: seleniu...@googlegroups.com
> > > Subject: Re: [selenium-users] Selenium Grid2 Node RegistrationFails
>
> > > You're supplying the wrong command line arguments for the hub. To
> > > start the hub, use:
>
> > > java -jar selenium-server-standalone-2.22.0.jar -role hub
>
> > > Check out the wiki page, it explains all of this:
> > >http://code.google.com/p/selenium/wiki/Grid2
>
> > > On Fri, Jun 1, 2012 at 2:49 PM, CuriousTester <pravirjo...@gmail.com>
> > > wrote:
> > > > Hi All,
>

> > > > I'm failing toregisternode on grid using latest Selenium server

> > > > version 2.22.0 on the same machine on which hub is running. Following
> > > > message is recieved -
>

> > > > 14:33:38.703 INFO - couldn'tregisterthis node : Error sending the
> > > > registration
> > > >  request.
> > > > 14:33:43.711 INFO - couldn'tregisterthis node : hub down or not

> > > > responding.
>
> > > > Here are the commands used -
>

> > > > Toregisterserver -

[Naresh Thandu]

Hi,

I was trying to give an example on how to use the roles.

And IP address is the local ip address on intranet.

Thanks

[Mike Riley]

Here is how I start the hub (note I increase the default heap size for Java):
java -Xms32m -jar selenium-server-standalone.jar -role hub -port 4444

You put in "-hub" and not "-role hub" in your example.  The port would default to 4444, but I still declare it.

Here is how I start the node (my hub server may be on a different system, hence I declare it by IP address in an environment variable):

java -Xms32m -jar selenium-server-standalone.jar -role node -hub http://%HUB_IP%:4444/grid/register -registerCycle 60000

Note that here I am using the -hub switch to tell it what URL and port the hub is at.  I recommend using "-role node", so it works for either RC or WebDriver modes.

So it looks to me like you sort of started two nodes here with no hub, based on what you posted earlier.

Mike

> To post to this group, send email to selenium-users@googlegroups.com.
> To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.

> For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.

To post to this group, send email to selenium-users@googlegroups.com.
To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.

[CuriousTester]

Thanks Mike but I've tried all those options excluding the heap size
increase and had no luck.

Note that I'm able toi bring server up without any issue, problem is
faced while regsitering the node. Tried on same as well as remote
machines with IP address.

On running the commmand that you suggested, I cannot load hub console
on browser; server is not started properly though no error is thrown
on cmd window. Refer details below

java -Xms32m -jar selenium-server-standalone.jar -role hub -port 4444

C:\Selenium>java -Xms32m -jar selenium-server-standalone-2.22.0.jar -
role hub -port 4444
Jun 04, 2012 5:26:04 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
2012-06-04 17:26:10.098:INFO:osjs.Server:jetty-7.x.y-SNAPSHOT
2012-06-04 17:26:10.129:INFO:osjsh.ContextHandler:started
o.s.j.s.ServletContextHandler{/,null}
2012-06-04 17:26:10.145:INFO:osjs.AbstractConnector:Started
SocketC...@0.0.0.0:4444


Version on server jar used is latest one - selenium-server-
standalone-2.22.0.jar

Has anyone tried this on latest version of Server?

> > On Fri, Jun 1, 2012 at 2:49 PM, CuriousTester <pravirjo...@gmail.com>

> > wrote:
> > > Hi All,
>
> > > I'm failing to register node on grid using latest Selenium server
> > > version 2.22.0 on the same machine on which hub is running. Following
> > > message is recieved -
>
> > > 14:33:38.703 INFO - couldn't register this node : Error sending the
> > > registration
> > >  request.
> > > 14:33:43.711 INFO - couldn't register this node : hub down or not
> > > responding.
>
> > > Here are the commands used -
>
> > > To register server -
> > > java -jar selenium-server-standalone-2.22.0.jar -hub
>
> > > To register node
> > > java -jar selenium-server-standalone-2.22.0.jar -role wd -hub http:/
> > > /localhost:4444/grid/register
>
> > > Note that I`ve checked server is up and running on browser.
>
> > > I could not find much help on this earlier posts so any help is
> > > appreciated
>
> > > Thanks!
>
> > > --
> > > You received this message because you are subscribed to the Google
> > Groups "Selenium Users" group.

> > > To post to this group, send email to seleniu...@googlegroups.com.

> > > To unsubscribe from this group, send email to

> > selenium-user...@googlegroups.com.

> > > For more options, visit this group at
> >http://groups.google.com/group/selenium-users?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Selenium Users" group.

> > To post to this group, send email to seleniu...@googlegroups.com.

> > To unsubscribe from this group, send email to

> > selenium-user...@googlegroups.com.

[Mike Riley]

That is exactly what I am using and I have it running just fine, with the same message on my console.

Here is the URL I use to view the console (I prefer the debug one and since I am still testing it is on 5555 right now):
http://10.0.2.208:5555/grid/console?config=true&configDebug=true

Here is what the web page looks like running it:

Grid Hub 2.22.0

DefaultRemoteProxy

listening on http://10.0.2.206:5556
test session time out after 300 sec.
Supports up to 5 concurrent tests from:
htmlunit

DefaultRemoteProxy

listening on http://10.0.2.209:5556
test session time out after 300 sec.
Supports up to 5 concurrent tests from:
htmlunit

DefaultRemoteProxy

listening on http://10.0.2.208:5556
test session time out after 300 sec.
Supports up to 5 concurrent tests from:
htmlunit

Config for the hub :
host : null
port : 5555
cleanUpCycle : 5000
timeout : 300000
browserTimeout : 0
newSessionWaitTimeout : -1
grid1Mapping : {}
throwOnCapabilityNotPresent : true
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
prioritizer : null
servlets :

all params :

browserTimeout : 0
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
cleanUpCycle : 5000
host : null
maxSession : 5
newSessionWaitTimeout : -1
nodePolling : 5000
port : 5555
prioritizer : null
role : hub
servlets : []
throwOnCapabilityNotPresent : true
timeout : 300000

Config details :
hub launched with :-role hub -port 5555
the final configuration comes from :
the default :
host : null
port : 4444
cleanUpCycle : 5000
timeout : 300000
browserTimeout : 0
newSessionWaitTimeout : -1
grid1Mapping : {}
throwOnCapabilityNotPresent : true
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
prioritizer : null
servlets :

all params :

browserTimeout : 0
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
cleanUpCycle : 5000
host : null
maxSession : 5
newSessionWaitTimeout : -1
nodePolling : 5000
port : 4444
prioritizer : null
servlets : []
throwOnCapabilityNotPresent : true
timeout : 300000

updated with grid1 config :No grid1 file specified. To specify one, use -grid1Yml XXX.yml where XXX.yml is a grid1 config file

updated with grid2 config : No hub config file specified. To specify one, use -hubConfig XXX.json where XXX.json is a hub config file

updated with params :
host : null
port : 5555
cleanUpCycle : 5000
timeout : 300000
browserTimeout : 0
newSessionWaitTimeout : -1
grid1Mapping : {}
throwOnCapabilityNotPresent : true
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
prioritizer : null
servlets :

all params :

browserTimeout : 0
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
cleanUpCycle : 5000
host : null
maxSession : 5
newSessionWaitTimeout : -1
nodePolling : 5000
port : 5555
prioritizer : null
role : hub
servlets : []
throwOnCapabilityNotPresent : true
timeout : 300000


Mike

> > > To post to this group, send email to selenium-users@googlegroups.com.

> > > To unsubscribe from this group, send email to

> > selenium-users+unsubscribe@googlegroups.com.

> > > For more options, visit this group at
> >http://groups.google.com/group/selenium-users?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Selenium Users" group.

> > To post to this group, send email to selenium-users@googlegroups.com.

> > To unsubscribe from this group, send email to

> > selenium-users+unsubscribe@googlegroups.com.

[ankit]

Perhaps this is an issue with firewalls? Try ensuring that you can ping the machines and that the port is open. You could also try running the hub on a port thats definitely open, like 80. It's probably not a good idea to permanently run the hub on this port, but if it works then you know what the problem is.

[Francis Aiello]

Hello Ankit,

Thanks for your suggestion.  Here are my results based on your suggestion...I'm not super strong on Linux but did research based upon your suggestions and ran the following commands that I believe perform the actions you've specified.

I've also chosen an unusual port (12345)

Hub: 

java -jar ./selenium-server-standalone-2.24.1.jar role -hub -port 12345

Ping:   Pinging from the 'node' server

ping 192.168.10.128

 

PING 192.168.10.128 (192.168.10.128) 56(84) bytes of data.

64 bytes from 192.168.10.128: icmp_seq=1 ttl=63 time=0.352 ms

64 bytes from 192.168.10.128: icmp_seq=2 ttl=63 time=0.253 ms

Ports:

sudo lsof -i

 

COMMAND     PID             USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME

java        716            frana    5u  IPv6 17558012      0t0  TCP localhost:55765->localhost:7056 (CLOSE_WAIT)

java        716            frana   12u  IPv6 17410671      0t0  TCP *:12345 (LISTEN)

...

sudo netstat -lptu

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

tcp6       0      0 [::]:12345              [::]:*                  LISTEN      716/java   

 

What I'm wondering is if this might be due to the fact that it is using IPv6 - could that be possible?  It doesn't appear to be a firewall issue from what I can tell.

Further advice/suggestions would be appreciated.

Thanks again for your suggestions.

Fran

[Amey]

The reason according to me is you are starting the node incorrectly
You have not defined the port on which the node/webdriver should run

Your command for starting the node should be 

java -jar selenium-server-standalone-2.22.0.jar -port 4445 -role wd -hub http://localhost:4444/grid/register

Note the inclusion of the port number on which you want to run the node.

[Amey]

Also what do you mean when you say "checked server is up and running" how did you do that ?

Also when you access "http://0.0.0.0:4444/grid/console" from you browser after starting the hub, do you get something like

HTTP ERROR: 403

Forbidden for Proxy

RequestURI=/grid/console

Powered by Jetty://

If so, you must reconsider your firewall settings.

On Friday, June 1, 2012 2:49:45 PM UTC-4, CuriousTester wrote:

[Francis Aiello]

Hello Amey, Ankit

Just wanted to say "thank you" as I believe you are both right.  

I performed a similar setup configuration on my Windows machine to purposely see if I got the same results in Linux and I was able to get the node to communicate with the hub.  However when I performed the setup Windows did challenge me with a message stating that a Java process was being blocked by the Windows firewall.  So as you both suspected - I'm sure that is what is going on in the Linux configuration as well.

As for the Linux installation I'm going to have to engage the Linux System Admins to assist.

I'll submit more on my Linux installation after I learn what is the root cause - in the hopes that it could help someone else.

Amey

Just so you know when you mentioned below hitting the http://0.0.0.0:4444/grid/console - that is what really triggered it for me in that I got the exact same message.  I just wasn't sure what it meant.

Thanks to both of you.

Fran

[Krishnan Mahadevan]

Kevin,

You are NOT starting a Grid hub but a standalone SELENIUM server.

1. // starting the server:
2. $ java -jar selenium-server-standalone-2.25.0.jar
3. 20:54:56 org.openqa.grid.selenium.GridLauncher main
4. INFO: Launching a standalone server
5. 20:55:02.188 INFO - Java: Apple Inc. 20.8-b03-424
6. 20:55:02.205 INFO - OS: Mac OS X 10.8 x86_64

The command to start the grid hub run the command : java -jar selenium-server-standalone-2.25.0.jar -role hub

For step by step instructions, you can refer to my post : http://rationaleemotions.wordpress.com/2012/01/23/setting-up-grid2-and-working-with-it/

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"

On Mon, Aug 6, 2012 at 12:51 AM, Kevin Smith <ke...@ksmth.de> wrote:

I am having the exact same issue. Here is a link to pastebin from the log generated when I try to launch the grid and the node: http://pastebin.com/XaLCFE2v

Am Mittwoch, 20. Juni 2012 00:39:27 UTC+2 schrieb Francis Aiello:

Curious Tester,

I've been reading through this issue and am facing similar conditions.  

My setup is on the same machine for simplicity in order for me to learn Selenium Grid.

To start up the "hub" I'm using the following command; 

java -jar ./selenium-server-standalone-2.24.1.jar role -hub -port 4444

To start up the "node" I'm using the following command;

java -jar ~/bin/seleniumgrid/selenium-server-standalone-2.24.1.jar -role node -hub http://192.168.10.128:4444/grid/register -registerCycle 60000

The output when I launch the "node" is the following;

Jun 19, 2012 3:20:30 PM org.openqa.grid.selenium.GridLauncher main

INFO: Launching a selenium grid node

Jun 19, 2012 3:20:35 PM org.openqa.grid.internal.utils.SelfRegisteringRemote startRemoteServer

WARNING: error getting the parameters from the hub. The node may end up with wrong timeouts.A JSONObject text must begin with '{' at character 1

15:20:40.999 INFO - Java: Sun Microsystems Inc. 20.1-b02

15:20:41.000 INFO - OS: Linux 2.6.32-37-generic amd64

15:20:41.004 INFO - v2.24.1, with Core v2.24.1. Built from revision 17205

15:20:41.082 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:5555/wd/hub

15:20:41.082 INFO - Version Jetty/5.1.x

15:20:41.083 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]

15:20:41.084 INFO - Started HttpContext[/selenium-server,/selenium-server]

15:20:41.084 INFO - Started HttpContext[/,/]

15:20:41.093 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@5eb7ec5d

15:20:41.093 INFO - Started HttpContext[/wd,/wd]

15:20:41.095 INFO - Started SocketListener on 0.0.0.0:5555

15:20:41.095 INFO - Started org.openqa.jetty.jetty.Server@7f70888e

15:20:41.096 INFO - using the json request : {"class":"org.openqa.grid.common.RegistrationRequest","capabilities":[{"platform":"LINUX","seleniumProtocol":"Selenium","browserName":"*firefox","maxInstances":5},{"platform":"LINUX","seleniumProtocol":"Selenium","browserName":"*googlechrome","maxInstances":5},{"platform":"LINUX","seleniumProtocol":"Selenium","browserName":"*iexplore","maxInstances":1},{"platform":"LINUX","seleniumProtocol":"WebDriver","browserName":"firefox","maxInstances":5},{"platform":"LINUX","seleniumProtocol":"WebDriver","browserName":"chrome","maxInstances":5},{"platform":"WINDOWS","seleniumProtocol":"WebDriver","browserName":"internet explorer","maxInstances":1}],"configuration":{"port":5555,"register":true,"host":"10.112.0.6","proxy":"org.openqa.grid.selenium.proxy.DefaultRemoteProxy","maxSession":5,"hubHost":"192.168.10.128","role":"node","registerCycle":60000,"hub":"http://192.168.10.128:4444/grid/register","hubPort":4444,"url":"http://10.112.0.6:5555","remoteHost":"http://10.112.0.6:5555"}}

15:20:41.097 INFO - starting auto register thread. Will try to register every 60000 ms.

15:20:41.098 INFO - Registering the node to hub :http://192.168.10.128:4444/grid/register

15:20:41.103 INFO - couldn't register this node : Error sending the registration request.

15:21:41.105 INFO - couldn't register this node : hub down or not responding.

15:22:41.108 INFO - couldn't register this node : hub down or not responding.

I would appreciate any guidance/advice on understanding what it is that I'm doing wrong.  

I've been reading through the Selenium Wiki in order to educate myself and believe I'm doing it correctly but obviously I'm missing something further. 

Thank you in advance for assistance,

Fran

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.

To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/55j6Wia1xCUJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Maciej Piątek]

I had the same problem and solution was to disable ipv6,

I followed the instructions from:

http://mysolvedproblem.blogspot.co.uk/2012/05/installing-hadoop-on-ubuntu-linux-on.html

i've noticed that netstat -lntp showed 0.0.0.0:4444 but in ipv6, but after finding the link above, disabling ipv6, everything runs smoothly and 0.0.0.0:4444 is in ipv4.

Good luck

Maciek

PS. My ubuntu is 13.04, selenium 2.33

[Maciej Piątek]

Try disabling ivp6, like here:

http://mysolvedproblem.blogspot.co.uk/2012/05/installing-hadoop-on-ubuntu-linux-on.html

it helped in my situation, check
netstat -lntp 
Mine was displaying 0.0.0.0:4444 in ipv6, after disabling ipv6 like below it started working again:

------

sudo vim /etc/sysctl.conf

This command will open sysctl.conf in text editor, you can copy the following lines at the end of the file:

#disable ipv6

net.ipv6.conf.all.disable_ipv6 = 1

net.ipv6.conf.default.disable_ipv6 = 1

net.ipv6.conf.lo.disable_ipv6 = 1

 These steps required you to reboot your system, but alternatively, you can run the following command to re-initialize the configurations again.

$sudo sysctl -p 

To make sure that IPV6 is disabled, you can run the following command:

$cat /proc/sys/net/ipv6/conf/all/disable_ipv6

----

good luck

ubuntu 13.04, selenium 2.33

[Raj Yadav]

For windows 7 you have to go to advanced settings and add a rule for inbound from other machine to allow firewall java commands
and in  remote machine add a rule for inbound from other machine to allow firewall java commands..works like a charm