I know how to open ports via going into the Properties thingy on my
connection doohicky, that ain't the problem. The problem is that every
day or two XP just takes it upon its fucking self to CLOSE the ports I
opened. And it is irritating me no end.
I have a firewall in my router, and I don't mind putting a third-party
firewall on my computer if need be, but this piece of shit self
adjusting XP firewall has got to go. Suggestions?
Nevermind, I think I finally managed to google up the answer.
Start:Run: services.msc
and then just shut the son of a bitch off.
AFAIK you just open up the LAN properties, go to the Advanced sheet and
uncheck Internet Connection Firewall. Sorry if that's what you HAVE been
doing. I too have a firewalled router so never bother with the XPee bundled
software solution.
In fact I'm quite pleased with myself since I finally managed to figure out
which port-forwarding and port-opening was necessary to do remote connecting
as well as indulge once more in the odd game of Risk II at the
http://zone.msn.com without having to rip out my router every time.
Aaaaaarrrghh.....
--
jonathan
--
"Never occupy North America in the first round"
>"Michael Cash" <mike...@sunfield.ne.jp> wrote in message
>news:jrinnv8f5egv2mc70...@4ax.com...
>> Does anybody know how to just yank the son of a bitch out by the
>> fucking roots?
>>
>> I know how to open ports via going into the Properties thingy on my
>> connection doohicky, that ain't the problem. The problem is that every
>> day or two XP just takes it upon its fucking self to CLOSE the ports I
>> opened. And it is irritating me no end.
>>
>> I have a firewall in my router, and I don't mind putting a third-party
>> firewall on my computer if need be, but this piece of shit self
>> adjusting XP firewall has got to go. Suggestions?
>>
>
>AFAIK you just open up the LAN properties, go to the Advanced sheet and
>uncheck Internet Connection Firewall. Sorry if that's what you HAVE been
>doing. I too have a firewalled router so never bother with the XPee bundled
>software solution.
I did have it unchecked there. But my router had something different
listed in the Network Connections. It had no Advanced sheet, only a
Settings button, which led to a place to add port openings. I opened
it to find that MSN Messenger, which I don't use, had already opened
up a couple for itself. I added the ports I needed open and everything
worked just fine. But once every day or two XP would take it upon
itself to delete the openings I had put in. It left the Messenger
ports open though.
I ran services.msc and right-clicked the Internet Connection Firewall
line, selected Properties, then disabled the bastard entirely. When I
did this, the aforementioned router icon disappeared entirely from my
Network Connections.
I tried installing and configuring ZoneAlarm. It was all just fine
except that it wouldn't let me....uh....scratch that....wouldn't let
my friend get a connection with WinMX, despite the program having full
access privileges. After a struggle, I finally got ZoneAlarm
uninstalled. I have used it in the past. I wonder how I forgot how
much I disliked the damned thing back then?
Now my router's firewall and Norton Firewall are handling things. MX
is working, but I'll need one of the Chosen Few to tell me if the ftp
server can be accessed or not.
Doesn't WinMX have an option for "this is behind a firewall (use Port 0)" or
something similar? That will allow you to connect even if you don't open up
any ports for it. Or at least WinNY worked that way for me.
- awh
>Michael Cash <mike...@sunfield.ne.jp> wrote:
It does. If you run a secondary connection instead of a primary
connection. For the primary, you gotta have the ports open.