Be Right Back, Uninstalling
Port 4000 TCP - Printable Version

+- Be Right Back, Uninstalling (https://www.brbuninstalling.com)
+-- Forum: Technology (https://www.brbuninstalling.com/forumdisplay.php?fid=51)
+--- Forum: Computers (https://www.brbuninstalling.com/forumdisplay.php?fid=69)
+--- Thread: Port 4000 TCP (/showthread.php?tid=10308)



Port 4000 TCP - Fail Medic - 07-11-2009

This isn't really a request for help so much as a signal to see if anyone else says, "Yeah, me too."

I can't expose port 4000 TCP to the outside.  I want to, but I can't.  I want to play Diablo II with a friend and port 4000 TCP is a critical key to this enterprise.

Windows firewall off.  Went through the whole port forward business on the router before removing it from the stream so computer's now hooked directly to cable modem.  I then use a PFPortChecker program downloaded from portforward.com.

4000 UDP... works.  Open.  Yay.
4000 TCP... Nothing.  No how.  No dice.

My friend and I asked our mutual ISP whether they're blocking port 4000.  They provided both of us a list of ports they've blackballed and 4000 ain't on it.

Culprits have been narrowed to a lying or misinformed ISP tech line or some subconscious limiter in my cable modem.  I guess something in my PC could still be blocking it, but firewall is totally shut off and no other software firewall exists on my PC.

Port 4000, you piece of unmitigated shit, what is your goddamn problem.

... Please respond if you've had to fight with a similar situation.  Thanks.


Re: Port 4000 TCP - zaneyard - 07-11-2009

did you get a time out for that program
or did it immediately go to closed?


Re: Port 4000 TCP - Fail Medic - 07-11-2009

(07-11-2009, 01:50 AM)zaneyard link Wrote: did you get a time out for that program
or did it immediately go to closed?

It sits on "connected to portforward.com, waiting for portcheck to complete" for five seconds.  This leads me to believe outbound's working but not inbound if it's going out through 4000 and then trying to come back for the test.  ... i dunno lol


Re: Port 4000 TCP - 3clipse - 07-11-2009

Diablo 2? I Wanna play Big Grin. Contact me when you do Big Grin


Re: Port 4000 TCP - Benito Mussolini - 07-11-2009

(07-11-2009, 03:11 AM)3clipse link Wrote: Diablo 2? I Wanna play Big Grin. Contact me when you do Big Grin
This

Sorry for not being able to help =(


Re: Port 4000 TCP - zaneyard - 07-11-2009

did you try using the game? after removing your router and software firewall that is?


Re: Port 4000 TCP - Fail Medic - 07-12-2009

(07-11-2009, 02:14 PM)zaneyard link Wrote: did you try using the game? after removing your router and software firewall that is?

Yes, we did.  Both him trying to host and I trying to host.


Re: Port 4000 TCP - Blues - 07-12-2009

I totally want to play through this game with people I haven't played in years. Let's just do bnet nigs I have like 50 thousand legit keys.


Re: Port 4000 TCP - 3clipse - 07-12-2009

(07-12-2009, 08:44 PM)Pokemon Trainer Blues link Wrote: I totally want to play through this game with people I haven't played in years. Let's just do bnet nigs I have like 50 thousand legit keys.
will play, gimme a key for my friend too. Big Grin


Re: Port 4000 TCP - at0m - 07-15-2009

semi-related: what ISP?


Re: Port 4000 TCP - Fail Medic - 07-15-2009

(07-15-2009, 10:16 AM)at0m link Wrote: semi-related: what ISP?

Cox Communications.


Re: Port 4000 TCP - KarthXLR - 07-15-2009

(07-15-2009, 05:18 PM)Fail Medic link Wrote: [quote author=at0m link=topic=3254.msg98141#msg98141 date=1247671004]
semi-related: what ISP?

Cox Communications.
[/quote]
:o


me too.


Re: Port 4000 TCP - at0m - 07-15-2009

(07-15-2009, 06:19 PM)Karth is a Public Enemy link Wrote: [quote author=Fail Medic link=topic=3254.msg98265#msg98265 date=1247696311]
[quote author=at0m link=topic=3254.msg98141#msg98141 date=1247671004]
semi-related: what ISP?

Cox Communications.
[/quote]
:o


me too.
[/quote]Are you also having problems? Or was this another attempt at earning a -1 with a completely useless post in a support thread?


Re: Port 4000 TCP - KarthXLR - 07-15-2009

(07-15-2009, 07:28 PM)at0m link Wrote: [quote author=Karth is a Public Enemy link=topic=3254.msg98295#msg98295 date=1247699973]
[quote author=Fail Medic link=topic=3254.msg98265#msg98265 date=1247696311]
[quote author=at0m link=topic=3254.msg98141#msg98141 date=1247671004]
semi-related: what ISP?

Cox Communications.
[/quote]
:o


me too.
[/quote]Are you also having problems? Or was this another attempt at earning a -1 with a completely useless post in a support thread?
[/quote]

Well, I've been disconnecting a lot recently, if that counts.


Re: Port 4000 TCP - beep beep diglett - 07-15-2009

(07-15-2009, 05:18 PM)Fail Medic link Wrote: [quote author=at0m link=topic=3254.msg98141#msg98141 date=1247671004]
semi-related: what ISP?

Cox Communications.
[/quote]

aaa me too lololol

-1 me for useless post

i used to have this issue with diablo 2 all the time, when i got a new comp w/ any protection it worked fine

so, my advice is to not take my advice


Re: Port 4000 TCP - Fail Medic - 07-16-2009

(07-15-2009, 08:37 PM)beep beep diglett link Wrote: so, my advice is to not take my advice

But, regardless of whether I can fix it, I wanna know who or what to blame  :'( . 

You're saying Computer A was blocked but Computer B (new one) wasn't blocked.  Well, I tried troubleshooting this with a laptop (different machine) on the same router / cable modem pair and 4000 TCP was still blocked.

No, I haven't tried getting different router / cable modem hardware, but I'd like to try to avoid that if the solution was obvious and easy to implement.

As it stands, I'm SOL.  My only hope is that Diablo III won't use the same port and go towards the 6000's where StarCraft is, but I'm sure Blizzard will leave it on 4000 TCP just to piss me off.


Re: Port 4000 TCP - HeK - 07-18-2009

You could always setup a tunnel to avoid the problem entirely.