| || |
Webload v8.4 TestTalk issues
This is one of my many stops in researching an issue we are having regarding running a test with the Client and TestTalk on another machine.
Basically whats happening is that when we try to run a test on the other machine (the load generator) it can't connect to the test talk service. We receive the error "All hosts are unreachable or stopped. Can't start session"
I was wondering if anyone has experienced this before and if so what did you do to correct it? The steps we've taken are listed below.
2 Windows 2003 servers segregated in a lab environment. Both can ping each other without issue.
Radview Webload v8.4
RTFM and tried the suggestions there.
Had our network group monitor traffic between the two machines and was able to see the ping but saw nothing when we attempted to run the test.
On both servers, the built in Windows Firewall is not active but have added ports 9000 and 9010 to it. Port 137 would not allow me to add because it is currently bound to Windows Print & File sharing but not active. (This may be the issue but I'm not sure.)
In the process of verifying if there is an external firewall between those two machines. I don't think there is but better to check than not.
I've run NetBrute scanner suite to verify those ports are open and it says they are on both machines however 137 is not. (Again, this may be my issue.)
If 137 is my issue and is bound to Windows Print & File Sharing, I know I can enable/reallocate it but I will need to double check with my network group to make sure it's ok. I'm not sure if they use it for anything.
We have run tests before using a Linux box set up off site and was able to successfully run that test so we at least know Webload is working and can send out commands.
If anyone has any thoughts or advice, I would greatly appreciate it.
Re: Webload v8.4 TestTalk issues
We got it figured out. Took me forever but it was really something simple. (Please feel free to raz me about the obvious!)
I finally got a chance to look at the testers test and they had the IP address of the TestTalk client machine incorrect. Once the correct IP address was entered, it worked.