Cannot Connect Other Computers to Selenium Grid - selenium

I am able to register nodes to the hub when I'm working on just one computer, but when I try to connect a node that is running on another computer I get a timeout or a message saying the hub must be down or not responding. I have no idea how to solve this.
After starting the hub I get the message: Nodes should register to http:192.168...:4444/grid register.
A tutorial said that
"you can check if Machine B can access the hub's web interface by launching a browser there and going to where "iporhostnameofmachineA" should be the IP address or the hostname of the machine where the hub is running. Since Machine A's IP address is 192.168.1.3, then on the browser on Machine B you should type >http://192.168.1.3:4444/grid/console."
But chrome is giving me a "This site can't be reached error". This must be an issue with my network configuration, but I do not how what I should do to fix it.

I would try using the command 'telnet 192.168.1.3 4444' from your Selenium node and see if it connects. On the machine running the hub, (so 192.168.1.3) run 'netstat -antp | grep 4444' (assuming it's a linux machine) and make sure you see an entry showing that the port is being listened on. If it's a windows machine you can still use netstat but not grep I think. Once you confirm that the hub is indeed listening on port 4444, and you can ping 192.168.1.3, but cannot telnet to port 4444, you have basically determined that there is a firewall issue. Then you would need to look into the firewalls on both machines, and any firewalls between them.

Related

Trying to connect to the pfsence web interface

I have installed and set up pfsence on virtual box and it is booting up properly and seems to be working fine. My problems are:
When I tried to ping the LAN IP from my computer's command prompt it does not receive the packets but if i ping it from inside the virtual machine using pfsence then it returns packets.
Also if I try the IP in the browser it does not take me to the pfsence interface. I used all defaults when installing the the pfsence.
Any suggestions will be welcomed
LAN IP - 192.168.20.20
pfsence version - 2.4.5
This means that you are unable to route into the VM from your computer. What is the Network Adapter for your VM attached to in your VirtualBox settings? If you configure it with a NAT you can achieve your desired configuration.
https://www.virtualbox.org/manual/ch06.html#network_nat

Port 80 stopped responding using Ubuntu 18.04 on Compute Engine

I am using Ubuntu 18.04 on GCP Compute Engine.
A simple go lang server listens to port 80 and responds to browser requests.
I was able to connect to the server on the Internet for a day. I stopped the instance couple of times and started. Now port 80 doesn't respond any more and browser times out.
When I start the program, there are no errors reported and my println statement in server faithfully prints a message "listening to port 80".
How can I troubleshoot this problem? Is there a problem with port 80 on Ubuntu?
Also ssh stopped responding. I can only use the web console.
Any help will be appreciated.
Unless you assign your instance a static IP address, your instance has an ephemeral IP address. Stopping your instance releases an ephemeral address. When you start your instance again you are assigned a new address.
The solution is either to use the new IP address or to change the address to be static.
Go to the Google Cloud Console -> Compute Engine.
Make a note of the external IP address.
Go to VPC Network -> External IP addresses.
Locate the IP address assigned to your instance. Under the type column, click on
"Ephermal" and change to "Static".

ServiceControl doesn't seem to do anything

I have ServiceControl setup on it's own VM and configured to use SQL Transport which I have pointed at the SQL database that's currently being used for NServiceBus. I've opened up port 33333 in the firewall on both the VM and in Azure NSG. I also installed OpenSSH and opened those ports.
On my local machine, I've opened a tunnel to the ServiceControl VM and forwarded port 33333. The tunnel opens without issue. I am running ServiceInsight on my local machine and have it connect to localhost:33333 which is forwarded to the remote VM. It connects without any reported error.
That's it. There is no data displayed in ServiceInsight. No endpoints in the endpoint explorer or anything.
Did I miss something? I'm not sure how to troubleshoot this.

How do I telnet to a specific port on a Windows 8 Consumer Preview machine?

I have been trying to troubleshoot a program that 'listens' on port 7751 for TCP connections. In Windows 7 and before, sometimes I have to enable the port in any firewall software that exists but otherwise it works OK.
In testing on Windows 8 Consumer Preview, my app is unable to start its 'listening' service, and I get the error: "No connection could be made because the target machine actively refused it".
I turned off the Windows Firewall totally, to eliminate it, but the problem still exists (no other security software is installed on this Win8 box).
In order to eliminate my program, I went through the "Turn on/off Windows features" applet in Control Panel, and installed Telnet Server and Client. I have started the Telnet service (and made it automatic), and also added "Everybody" and myself specifically into the TelnetClients local group.
When I run from the command line:
telnet 192.168.100.93 7751
I am told "Could not open connection to the host, on port 7751".
I tried the following:
netstat -an | find /i "listening"
But the port 7751 was not listed (and program that should listen on it was running).
This port is not blocked by the firewall, as it is turned off.
I tried telnet to another port that was listed by the netstat command, and it works OK.
My application connects to the port using the following:
System.Net.Sockets.TcpClient tcpc = new TcpClient();
tcpc.Connect(server, port);
But the .Connect immediately sends it to the
catch(SocketException s)
Which reports the "No connection could be made because the target server actively refused it." Note the "target server" is itself.
My App is a regular Windows Forms app, in C#, which is built by Visual Studio 2005 (.net 2.0) on the Windows 8 box itself...
What am I doing wrong?
EDIT: In answer to the question below, the code which starts the listening is:
private TcpListener tcpL;
IPEndPoint ipEndPoint = new IPEndPoint(ipAddress, Configuration.portNumber);
tcpL = new TcpListener(ipEndPoint);
tcpL.Start();
(ipAddress and Configuration.portNumber are my IP address 192.168.100.93, and 7751 respectively).
This code is within a try/catch and does not go to the catch, so I assume it started OK?
Assuming that the commands you listed are returning valid data and 192.168.100.93 is the IP address of your machine (you could use 127.0.0.1 instead), your client won't be able to connect, as there isn't anything listening on the port.
Is your listening application using TcpClient to listen on a port? If not then the problem is on your listening application, so please show that code instead.

Net.Sockets : PC Portnumber changes dynamically in LAN via (DLINK)router

Hi i am creating server/client application using .net.Sockets something like cybercafe software.
Im following this example on codeproject Simple Socket Chat Program
there is no problem i run it on local pc. But when i run the client in the other pc in network i got a problem.
says :
No connection could be made because the target machine actively refused it.
I tried to use netstat -a on cmd and i found out that the portnumbers of all the p.c on our network always changes.
Is there any way to do it without using portnumber and just hostname or ipaddress only.
I need help...
Thanks in Regards
First, the random port numbers under Local Address in netstat are done so that everything gets a unique local port.
Also, a port is necessary for sockets.
The problem you are having is most likely because the firewall where your server software is located is blocking that port. For Windows 7 (and presumably Vista), you can unblock the port by running WF.msc, going to Inbound Rules on the left, clicking New Rule on the right, and adding a new program or port rule. The rest of the steps should be self-explanatory.