Son wrote:I might be mistaken, but being banned would not stop you from seeing the server...just joining it.
It depends on the ban. If it's a CD-Key hash ban, you're only banned from joining the game, but not on the network level. If it's an IP ban, you cannot connect to the server on the network level - resulting in a timeout error; if you can't even see the server at all on both xfire and swbf2, then you've been completely blocked off - not one part of your network connection communicates with the server.
SWBF2's client lobby checks with each and every server by sending specific packets to the query ports. In other words, if one of the servers have blacklisted your IP address, the packets don't go through to the server, and thus, it will not be listed. The same applies to Xfire query as well.
Gunner1010 wrote:My traceroute to the JBA server fails, most likely a router needs updating and most likely it's a rogers router.
This confirms my assumption. You are no doubt IP banned somehow, or your ISP needs to fix some network issues on their end. Either way, contacting the company might solve this.
Also, just double checking, but you didn't modify any settings in the router configuration? It's definitely possible to prevent any network connection from entering your network, given if the configuration is correct.
Here is what everyone should see when they do a traceroute to JBA: (updated)
- Code: Select all
Tracing route to 64.120.63.71.rdns.ubiquityservers.com [64.120.63.71]
over a maximum of 30 hops:
8 36 ms 32 ms 34 ms xe-2-3-0.cr1.sjc2.us.above.net [64.125.31.18]
9 43 ms 39 ms 44 ms xe-0-3-0.cr1.lax112.us.above.net [64.125.26.25]
10 65 ms 81 ms 69 ms xe-3-2-0.cr1.iah1.us.above.net [64.125.26.121]
11 78 ms 73 ms 73 ms xe-1-2-0.cr1.dfw2.us.above.net [64.125.26.129]
12 68 ms 69 ms 83 ms xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]
13 82 ms 77 ms 75 ms 209.66.115.54.t01344-01.above.net [209.66.115.54
]
14 69 ms 71 ms 69 ms 64.120.63.71.rdns.ubiquityservers.com [64.120.63
.71]
Trace complete.
It could vary here and there, but there shouldn't be a lot of timeouts.