I haven't been able to launch WinEQ2 since some time late yesterday. I'm getting the message:
"Could not connect to Lavish Software. Make sure your firewall is not blocking WinEQ 2 from making outgoing connections, and try again."
I haven't made any configuration changes at this end. Just one moment it was all working nicely, I camped for dinner and then couldn't get back online to play afterwards.
When I first tried, I had WinEQ2 already running and I was getting immediate timeout messages at the EQ client login screen. I rebooted and then wasn't able to connect to LavishSoft, but I'm now able to run EQ directly and log in and play with no problem - but I don't have access to the WinEQ2 features.
Am I alone in this? Do I have te chase something down at my ISP?
On the topic of my firewall, where would I find the IP and port that WinEQ2 is trying to connect to in order to verify it's license? I might have to raise the issue with my ISP.
WinEQ2 Can't Connect to Licensing Server
Moderators: Lavish Software Team, Moderators
It's extremely unlikely that your ISP is blocking our connections. Workplace firewalls would be a possibility, but assuming you're at home, no chance.
If you cannot connect to our server or the EQ server, then there's the possibility that your ISP's DNS server is down. Of course, that seems unlikely since you are able to connect to our web site, but certainly not unheard of if our web address was cached on your system. This would also prevent you from accessing plenty of web sites, and make it appear as though your internet is "down" (though technically still fully functional).
Anyway, a couple possibilities.
1. Windows firewall or other software firewall began blocking traffic when you went to dinner
2. Your ISP's DNS server is busted
3. You are getting heavy packet loss which causes connections to fail, drop, or slow to a crawl
I'd put my money on #3 based on your descriptions.
Grab this file:
http://www.lavishsoft.com/downloads/trout.exe
If your browser has an option to simply Run or Execute the file, click that. When it launches, a window will pop up and let you type in a little box. Type "lavishsoft.com" and hit enter. Immediately the main area of the window will have some text in it about the route between you and our server, and a red stop sign icon will appear on the toolbar in the window. When the red stop sign icon disappears it will be a blue lightning bolt, meaning that the process has finished. After it has finished, copy the results to the clipboard either by pressing CTRL+C, or by clicking on the 3rd icon from the left (between the disk and the W), or by going to Edit->Copy. Then simply paste the result for me here.
If you cannot connect to our server or the EQ server, then there's the possibility that your ISP's DNS server is down. Of course, that seems unlikely since you are able to connect to our web site, but certainly not unheard of if our web address was cached on your system. This would also prevent you from accessing plenty of web sites, and make it appear as though your internet is "down" (though technically still fully functional).
Anyway, a couple possibilities.
1. Windows firewall or other software firewall began blocking traffic when you went to dinner
2. Your ISP's DNS server is busted
3. You are getting heavy packet loss which causes connections to fail, drop, or slow to a crawl
I'd put my money on #3 based on your descriptions.
Grab this file:
http://www.lavishsoft.com/downloads/trout.exe
If your browser has an option to simply Run or Execute the file, click that. When it launches, a window will pop up and let you type in a little box. Type "lavishsoft.com" and hit enter. Immediately the main area of the window will have some text in it about the route between you and our server, and a red stop sign icon will appear on the toolbar in the window. When the red stop sign icon disappears it will be a blue lightning bolt, meaning that the process has finished. After it has finished, copy the results to the clipboard either by pressing CTRL+C, or by clicking on the 3rd icon from the left (between the disk and the W), or by going to Edit->Copy. Then simply paste the result for me here.
Thanks, Lax. In fact it was option #2. I changed my DNS servers and everything started working. (I knew the fix the instant Trout came back unable to resolve host names.) My ISP arrangement is a bit complicated and it looks as if they have partitioned some of their internal network so the DNS servers I was using are no longer visible to me.
My NAT firewall had updated the DNS since it's dynamic on the public side, but those changes didn't get reflected internally.
I didn't think of DNS since my email and web browser were working, but in retrospect, the browser is going through a proxy and the mail through a VPN.
I just needed a good slap up the side of the head to wake me up this morning.
My NAT firewall had updated the DNS since it's dynamic on the public side, but those changes didn't get reflected internally.
I didn't think of DNS since my email and web browser were working, but in retrospect, the browser is going through a proxy and the mail through a VPN.
I just needed a good slap up the side of the head to wake me up this morning.