Salem

Firstly, MERRY CRIMBO!

Secondly, I cant log in. Im normally I use my desktop and have no issues but IM over in my folks for christmas and in between getting fat and drunk as a lord I wanna leg in but I get that titular issue. Weird thing is I can log in at my home just not in my parents...

So im guessing its a router/firewall issue, SO. Things Ive tried

1. Comodo Firewall, gave rights to java, javaw, salem
2. Opened ports 1871/1870 (for both TCP/UDP)
3. cleared cache, reinstalled java, reinstalled client
4. tried both enders and standard client
5. punched the screen in frustration as im stuck at my folks with several hours to burn and not salem

My ip address here at my folks is 10.0.0.5 (weird right?), normally ive always seen it in the 192.168.x.x format so ive no idear whats going on...

HELP!

uncleseano wrote:1. Comodo Firewall, gave rights to java, javaw, salem

There's your problem. There's a possible fix floating around, but the easiest solution would be to uninstall it (and replace with a different security suite, of course... but not ESET). Give me a few minutes to dig it up. (I'm posting this just in case you're whacking F5 waiting for a post.)

edit: found this faster than I thought I would. Check out this post on Paradox Plaza. There's a couple possible fixes that might work for you.

Ace thanks for the response. Like I said my laptop and desktop work with comodo at home, it's just for today now that im at my parents so I guessed it was something altogether...will check the thread now. really don't wanna uninstall comodo just to play salem at my folks

*edit I did have that issue before but its not the splash problem. the client loads, both enders and the default one, its just when you go to log in I get that issue. I use the -xnosplash to get past that rec failed crap. no problems there

Might need to check the router, then, and make sure ports are open on it.

Yeah I guessed it was the router at the start and gave it a good going over. I changed the routers IP addresses from 10.x.x.x to the 192.168.x.x (probably not important) but ther thing that did it was in the port forwarding section I have ports from 1870 to 1871 for both UDP/TCP connection in the modem. Thing was it needed to be 1870 for TCP and 1871 UDP individually on two seperate lines. Or maybe I did something else, either way its working, sound