Haha, A one word email or pm would have been sufficient. I just wanted a quick yes or no, so I don\'t waste my time. I never sent any results, only an \"is it ok if I...\"



we now have this place:  http://hydlaa.com/smf/index.php?board=23.0   --neko

Originally posted by Lliran
Don\'t disable the firewall. That would be really, really bad. Work around the problem but NEVER (and I mean never) disable the firewall while you have a connection to the internet.

I only disabled the firewall to test, and that was the firewall on my local machine.

You will most likely end up with a compromised (i.e. infected) system in less than an hour if you disable the firewall while connected to the internet -- and then quite reasonably you will want to bifuricate whomsoever told you that disabling the firewall is a reasonable thing to try!

Heh, nah, def not an hour, i\'m still ping silent, and non-broadcasting, there\'s so many easier fish they wouldn\'t bother. And i have the software firewall on top of  that.

Also, do you have a firewall running on your local machine? If you don\'t then making your host a part of the DMZ is not good -- i.e. very bad.

Yes I have a software firewall. Sygate Personal and ZoneAlarm (which i abhor).

May I ask, why did you turn of NAT (network address translation)? If you don\'t have it on, then the port forwarding won\'t work unless your local computer has an IP address that lies in an internet-accessible range (and it won\'t).

I turned nat off and had the modem forward all traffic to my computer, at that point i didn\'t have port forwarding configured as i was getting all traffic shipped to my computer as it was the DMZ, and nothing was being filtered out by the modem.
That was an \"i\'m frustrated and don\'t care if i get attacted\" test. And that failed.

Do this:
1. Turn NAT back on.
2. Turn port forwarding on and forward port 7354 to your local computer.
3. Do not turn NAT off - never, jamais, niemals!
4. Don\'t listen to well-meaning but misinformed people that suggest turning the firewall off as a solution to any problem you are having.

That\'s what i did the first time, because those are the instructions, heh, had that worked i wouldn\'t have done anything else. But it didn\'t.
I\'m still blaming the ISP but i\'m confused as to why it can get the name of my characters but freeze after that. Quite confusing.

And steuben had a good point because if i can\'t get it to work with no firewall or router then that\'s where the problem is, or else the problem lies at the modem box config and from there the ISP.

Hah, and now i can\'t get on from work, which worked before. Splendid. Gah. I can\'t ping it but i can get to the website, grrr.

Ok so I went and configured all the settings and whatnot to let traffic through on 7354. I setup my dsl modem box to register planeshift on that port and forward it to my computer, however currently i turned off all nat related to my computer (from the modem box). Then I went into my router (Netgear rp614) and setup port forwarding, to my box and till no dice. My software firewall i have turned off however i have it open to check the ports being used and services trying to connect. It says that psclient.exe (planeshift client) is listening on 2264 and 2265 to begin with. Then after I log-in and get authenticated it stops listening on 2265. So now it\'s left listening on 2264 and that just doesn\'t seem right. I played around a little with the port forwarding for 2264 and 2265 with no dice. I can ping laanx.fragnetics.com with no issues and tracert also. And yes i am fully updated. Any ideas?