Can't find list server
Can't find list server
Hello, we'd appreciate some advice here.
We've just moved house. Until then Bzflag was running fine. Now, although our broadband connection is up and running, whenever we try find a server nothing happens. The game simply prints 'Can't talk with list server' (I've now changed this to what it actually says instead of what I thought it said!). It works okay on localhost.
Any suggestions or, better still, solutions?
BTW, we have reinstalled it, but there is no change.
Regards, armadillo.
We've just moved house. Until then Bzflag was running fine. Now, although our broadband connection is up and running, whenever we try find a server nothing happens. The game simply prints 'Can't talk with list server' (I've now changed this to what it actually says instead of what I thought it said!). It works okay on localhost.
Any suggestions or, better still, solutions?
BTW, we have reinstalled it, but there is no change.
Regards, armadillo.
Last edited by armadillo on Mon Nov 19, 2007 5:41 pm, edited 1 time in total.
Thy the global not identifying section of this page: http://my.bzflag.org/w/Common_Support_Issues
That is the most likely problem
That is the most likely problem
There is nothing worse than aggressive stupidity. -- Johann Wolfgang von Goethe
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
Thanks for the suggestion, but no joy.
I've tried changing the relevant config line to read: 'set list http://my.bzflag.org:81/db' but it makes no difference and bzflag then simply resets the line to its former state.
Cheers.
I've tried changing the relevant config line to read: 'set list http://my.bzflag.org:81/db' but it makes no difference and bzflag then simply resets the line to its former state.
Cheers.
Progress?
Yes, no problem constitution. I can bring up that link.
I've had a chance to run bz with debugging switched on. Here is the relevant part:
* About to connect() to my.bzflag.org port 3182 (#0)
* Trying 192.168.1.71... * Connection refused
* couldn't connect to host
* Expire cleared
* Closing connection #0
File transfer terminated with error from libcurl 7 : couldn't connect to host
Unmapped Locale String: Can't talk with list server
To my untrained eye it looks as though bz tries to connect locally; 71 is the machine I'm using. Shouldn't it be using the gateway: 254?
Thanks.
I've had a chance to run bz with debugging switched on. Here is the relevant part:
* About to connect() to my.bzflag.org port 3182 (#0)
* Trying 192.168.1.71... * Connection refused
* couldn't connect to host
* Expire cleared
* Closing connection #0
File transfer terminated with error from libcurl 7 : couldn't connect to host
Unmapped Locale String: Can't talk with list server
To my untrained eye it looks as though bz tries to connect locally; 71 is the machine I'm using. Shouldn't it be using the gateway: 254?
Thanks.
Here's some quick questions for you:
1: How far did you move? Did you just move a few miles away, or to the other side of the country?
2: During the process, did you have to change ISPs?
3: Did you keep your old router settings, or did you have to change them?
4: What is your DNS server (if you know)?
Maybe that will help shed some light on the problem.
1: How far did you move? Did you just move a few miles away, or to the other side of the country?
2: During the process, did you have to change ISPs?
3: Did you keep your old router settings, or did you have to change them?
4: What is your DNS server (if you know)?
Maybe that will help shed some light on the problem.
If you are able to connect in the browser, that's a good sign. I would be more inclined to assume that a firewall is the cause of this problem, since the BZFlag client itself does an HTTP request identical to what you did via the browser. Try disabling any and all firewalls on your machine temporarily and see if that allows BZFlag to connect.
Thanks, folks, for having a go at this. My boys are heartbroken at the moment. BZ is one of their favourites (and mine).
> 1: How far did you move? Did you just move a few miles away, or to the other side of the country?
> 2: During the process, did you have to change ISPs?
The simple answer to both these is that we have changed our ISP, so some of the basic router settings have also changed. Since then I have also upgraded the distro we use, so a new version of bz has been installed. I have tried setting aside the original config file and letting the new version of bz create a new one, but that has not worked either.
>3: Did you keep your old router settings, or did you have to change them?
The firewall settings on the router have not been altered. As mentioned above our new ISP uses a different setup, but these are just the basic DSL settings---so far all my other internet enabled apps are working okay.
>4: What is your DNS server (if you know)?
The router acts as the local DNS (at 192.168.1.254), but I don't off hand know the IP address for the ISP's DNS. [later] A bit of digging reveals: 212.50.160.100 as primary), and 213.249.130.100 as secondary DNS with our ISP.
Re the firewall: it's a good suggestion. So far I haven't found a way to turn off the router's firewall!
Cheers.
PS -- it seems the only way to 'turn off' the router's firewall is to create a DMZ. To be honest I don't see much point in trying this as the firewall has never been an issue in the past.
> 1: How far did you move? Did you just move a few miles away, or to the other side of the country?
> 2: During the process, did you have to change ISPs?
The simple answer to both these is that we have changed our ISP, so some of the basic router settings have also changed. Since then I have also upgraded the distro we use, so a new version of bz has been installed. I have tried setting aside the original config file and letting the new version of bz create a new one, but that has not worked either.
>3: Did you keep your old router settings, or did you have to change them?
The firewall settings on the router have not been altered. As mentioned above our new ISP uses a different setup, but these are just the basic DSL settings---so far all my other internet enabled apps are working okay.
>4: What is your DNS server (if you know)?
The router acts as the local DNS (at 192.168.1.254), but I don't off hand know the IP address for the ISP's DNS. [later] A bit of digging reveals: 212.50.160.100 as primary), and 213.249.130.100 as secondary DNS with our ISP.
Re the firewall: it's a good suggestion. So far I haven't found a way to turn off the router's firewall!
Cheers.
PS -- it seems the only way to 'turn off' the router's firewall is to create a DMZ. To be honest I don't see much point in trying this as the firewall has never been an issue in the past.
Last edited by armadillo on Tue Nov 20, 2007 2:30 pm, edited 1 time in total.
Have you tried http://portforward.com/ for help with your firewall settings? That is a pretty useful site.
There is nothing worse than aggressive stupidity. -- Johann Wolfgang von Goethe
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
Thanks for the suggestion, but I don't think it's a firewall issue.
BZ has been running on this machine for two or three years; with this router and network setup for a year, and the only thing that had changed when this problem started was our location and ISP. Also, I would expect the fresh install of the OS (though the 'Home' directory remained), would have enabled the fresh install of BZ to cater for the current setup.
BZ has been running on this machine for two or three years; with this router and network setup for a year, and the only thing that had changed when this problem started was our location and ISP. Also, I would expect the fresh install of the OS (though the 'Home' directory remained), would have enabled the fresh install of BZ to cater for the current setup.
- Joe Mama
- Private First Class
- Posts: 31
- Joined: Mon May 07, 2007 9:37 pm
- Location: Somewhere over the rainbow...
This happened to me several days ago. If you use a modem then try turning of the modem and turning it back on. Tha's what I did and it worked fine after that. If you have wireless then I can't help you.
If you don't know the answers to life's questions, guess.
Don't follow your dreams. Chase them.
Me pwning you is the way it was meant to be...
Don't follow your dreams. Chase them.
Me pwning you is the way it was meant to be...
If your ISP cares about your internet connection (anti-spam, firewall, anti-virus), it may block Bad Things from reaching you. Here's what I would suggest:
Try entering Join Game and use the following settings:
Server: pythonian.com
Port: 5154
(I don't care what you say, I know it's going to be there for a long time). If you cannot connect to the actual game server, we have a problem. If you can, we have a rarer problem.
Can you please tell me what ISP you're using, and what ISP you switched from?
Try entering Join Game and use the following settings:
Server: pythonian.com
Port: 5154
(I don't care what you say, I know it's going to be there for a long time). If you cannot connect to the actual game server, we have a problem. If you can, we have a rarer problem.
Can you please tell me what ISP you're using, and what ISP you switched from?
At this point, we've already ruled out a problem with the ISP. They can connect to the list server just fine from a web browser. To the ISP, the request that BZFlag makes will look the same, except for maybe some different HTTP headers.F687/s wrote:Can you please tell me what ISP you're using, and what ISP you switched from?
armadillo, not sure if you're tried this, but deleting the configuration file from the one system might help out as well.
I've spoken to Karoo's tech support. The person I spoke to wasn't one hundred percent sure, but as far as he knew they don't muck around trying to block certain transfers, etc.
So, I still feel none the wiser. We can log on to specified game servers, but we can't bring up the list server.
I don't want this to drag on but as F687/s said '...If you cannot connect to the actual game server, we have a problem. If you can, we have a rarer problem.' It seems to be the rarer problem.
Cheers and thanks.
So, I still feel none the wiser. We can log on to specified game servers, but we can't bring up the list server.
I don't want this to drag on but as F687/s said '...If you cannot connect to the actual game server, we have a problem. If you can, we have a rarer problem.' It seems to be the rarer problem.
Cheers and thanks.
Actually I think they're entirely different. Different servers, different ports, different connection methods. That's kind of like saying "If you can't get on the internet at all, we have a problem. If you can, we have a rarer problem."armadillo wrote:I don't want this to drag on but as F687/s said '...If you cannot connect to the actual game server, we have a problem. If you can, we have a rarer problem.' It seems to be the rarer problem.
Join us on IRC, ask us your question, wait patiently, and someone should hopefully be able to find you a solution.
Not true at all. Obviously, a problem connecting to a game server would show a problem with BZFlag itself (maybe). Furthermore, we would expect an unknown game protocol on unregistered ports to be blocked, but an HTTP request? Also, the request can be easily served via a web browser, but when the client tries to access that same address, it is denied. I am not experienced at all with ISPs in other continents, but if they say that they do not provide HTTP filtering, then I would believe them. By "distro" I assume you're using Linux (until Microsoft releases Windows 95 as open source), so who knows how your machine's configured. So now it is a matter of deduction to isolate what area of the connection is going wrong through logical deduction, and then fixing it.Constitution wrote:Actually I think they're entirely different. Different servers, different ports, different connection methods. That's kind of like saying "If you can't get on the internet at all, we have a problem. If you can, we have a rarer problem."