Problems connecting to battle.net / port forwarding question

[nfogserver]

I'm new to the whole Windows 2008 R2 scene. At first I tried opening the ports and adding inbound/outbound rules for the ports 6112-6119.

I turned off the firewall to verify. Still doesn't work.

I even went to grc https://www.grc.com/x/ne.dll?rh1dkyd2

scanned 6112-6119 and its closed

What do i do? Did I miss anything?

[Edge100x]

You won't need to forward any ports if you aren't running a firewall.

If an external port-scanning service indicates that those ports are closed, that means that nothing is running on them. Are you certain that you are specifying the IP and ports to bind to properly in your application?

Win2k8 is a bit picky about requiring that applications specify which IP(s) they want to use.

[nfogserver]

My Goal
To run Stealthbot

Problems Can't connect as showed below


What I did
Turned off firewall


My Logs
I ran the battle.net diagnostics tool

Code: Select all

------------------------------------------------------------------
                          System Overview                         
------------------------------------------------------------------
User                      : Administrator
Computer Name             : TILT
System Directory          : C:\Windows\system32
Windows Directory         : C:\Windows
Operating System          : 6.1 (Windows Vista)
OS Build                  : 7600
Platform ID               : 2
Service Pack              : 
Service Pack Version      : 0.0
Product Suites            : Remote Desktop (Single), Terminal Services.
Platform Type             : NT Server
Physical Memory Usage     : 47%
Total Physical Memory     : 1073340416
Total Virtual Memory      : 2147352576
Page File Size            : 2147082240
Available Physical Memory : 567754752
Available Virtual Memory  : 2105196544
Available Page File       : 1647632384



------------------------------------------------------------------
                       Processor Information                      
------------------------------------------------------------------
Processors             : 1
Processor Architecture : x86 (Intel)
Processor Family       : Pentium
Page Size              : 4096
Min. Memory Address    : 65536
Max. Memory Address    : 2147418111
3D Now!                : No
MMX                    : Yes
SSE3                   : Yes
SSE2                   : Yes
SSE                    : Yes
Channels               : No
Soft. Float Emulation  : No
DEP Enabled            : Yes
PAE Enabled            : Yes



------------------------------------------------------------------
                          Process Snapshot                        
------------------------------------------------------------------
[System Process]
System
smss.exe
csrss.exe
csrss.exe
wininit.exe
winlogon.exe
services.exe
lsass.exe
lsm.exe
svchost.exe
svchost.exe
LogonUI.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
spoolsv.exe
svchost.exe
shutdownmon.exe
svchost.exe
svchost.exe
csrss.exe
winlogon.exe
taskhost.exe
rdpclip.exe
dwm.exe
explorer.exe
msdtc.exe
StealthBot v2.7.exe
StealthBot v2.7.exe
sppsvc.exe
mmc.exe
BnetDiagTool.exe
conhost.exe



------------------------------------------------------------------
                          Application Log                         
------------------------------------------------------------------
Running version 2.2

+++ Begin application initialization.
Initializing console... 
Assigning console control handler... 
Loading the Winsock library... 
Initialization complete.

+++ Begin connection test with all servers on useast.battle.net

+++ Begin hostname resolution on useast.battle.net
Querying information about the host... 
Hostname successfully resolved, displaying results...
63.240.202.138
63.240.202.128
63.240.202.122
63.240.202.121
63.240.202.127
63.240.202.126
63.240.202.131
63.240.202.120
63.240.202.130
63.240.202.129
63.240.202.139
63.240.202.134

+++ Begin connection test with Battle.net server 63.240.202.138
Creating socket... 
Binding socket to any available address... 
Placing socket into asynchronous mode... 
Initiating connection... 
Attempting to establish a connection with the server... Error! 0

+++ Begin connection test with Battle.net server 63.240.202.128
Creating socket... 
Binding socket to any available address... 
Placing socket into asynchronous mode... 
Initiating connection... 
Attempting to establish a connection with the server... Error! 0

+++ Begin connection test with Battle.net server 63.240.202.122
Creating socket... 
Binding socket to any available address... 
Placing socket into asynchronous mode... 
Initiating connection... 
Attempting to establish a connection with the server... Error! 0

+++ Begin connection test with Battle.net server 63.240.202.121
Creating socket... 
Binding socket to any available address... 
Placing socket into asynchronous mode... 
Initiating connection... 
Attempting to establish a connection with the server... 

[Edge100x]

I notice in your log that it says "Binding socket to any available address... ", so you aren't binding to a single IP yet as I suggested. Please try that first.

[nfogserver]

Thank you for your time.
These are the only two options in my application settings that would allow me to maybe "bind" an IP



and



Again both firewalls are turned off. (The public and the domain firewalls)

Also, I'd like to mention that if I cannot connect using the bnet diagnostics tool:


So it doesn't really matter if I can bind into the application to the IP or not. If I can't run the Bnet diagnostic tool at all, I won't be able to connect to the BLizzard Servers.

Again I'd like to mention that my firewall is turned off completely. Unless I'm missing a step, then i don't know what to do. How do I make an application bind to an IP? Is it within the application or do I need to hit properties or something?

Please need assistance!

[Edge100x]

Specifying the IP to bind to would be need to be done in the application's settings.

It seems like some firewall is preventing you from connecting, and if you have yours turned off, it seems as though the firewall would have to be on the other end here (on battle.net's end). Have you double-checked with them to make absolutely certain that none of your IPs are blocked?

[Edge100x]

Another thing -- are you running all of these applications as an administrator?

Have you also tried Win2k3?

[nfogserver]

Why wouldn't it be working on Windows Server 2008?

Yes I was running it on admin mode.

Any other suggestions?

[Edge100x]

Why wouldn't it be working on Windows Server 2008?

I am suggesting general troubleshooting steps, knowing that other renters have run this application successfully. I am also hoping that one of them might chime in.

Yes I was running it on admin mode.

Any other suggestions?

It might be worth asking about this on one of the battle.net-oriented forums, where others who have experience with troubleshooting this software can provide more targeted assistance. This isn't a type of game server that we offer here, so I do not know it very well and can only offer generalized advice.

[senkin]

Hi, I run a server with name Senkin. I have had it for several months.

I did the exact same install procedure for the exact same OS as this customer. I even did it from scratch for him after he re-imaged the machine.

For some reason my computer connects with no real issues. Then when I use my VPS called Senkin2, it cannot. So for some reason nfogserver and my Senkin2 cannot connect to battle.net. I really don't think it is IP ban because they will let you connect then kick you out with ban message.

[Edge100x]

It makes sense that you would have the same problem if you use the same OS and version of the software. Has anyone tested with Windows 2003 yet, as I suggested? And has anyone contacted the battle.net guys, as I mentioned? They are pretty responsive and can answer whether the IP is banned.

This would either be a block by battle.net or a software glitch of some sort, so some combination of different settings, a different version of the software, or a location change (if avoiding a ban) should address it.

This shouldn't be anything we can control from our end here at NFO, but I'm continuing to investigate.

[Edge100x]

I just did some testing with the diagnostic tool from VDS and non-VDS machines in NYC, Dallas, Chicago, and San Jose.

NYC: Did not work
Dallas: Did not work from one block; worked from the other block
Chicago: Worked
San Jose: Did not work

Tracerts indicate that this isn't an outbound routing problem:

Chicago:

Code: Select all

C:\>tr 63.240.202.139

NFO win32 trace tool v2.04, copyright (c)2005 Nuclearfallout Enterprises, Inc.

Tracing route to 63.240.202.139 [63.240.202.139]
with up to 30 hops:

 1   0.3 ms   0.3 ms   0.3 ms  border6.ge1-14.nuclearfallout-41.chg.pnap.net [216.52.148.254]
 2   0.3 ms   0.3 ms   0.3 ms  core5.te2-1-bbnet1.chg.pnap.net [64.94.32.14]
 3 158.3 ms   2.2 ms 268.1 ms  207.88.184.145.ptr.us.xo.net [207.88.184.145]
 4   0.3 ms   0.2 ms   0.2 ms  207.88.84.213.ptr.us.xo.net [207.88.84.213]
 5   0.9 ms   0.8 ms   0.8 ms  te-4-2-0.rar3.chicago-il.us.xo.net [207.88.12.137]
 6   0.7 ms   0.8 ms   0.6 ms  ae0d1.cir1.chicago2-il.us.xo.net [207.88.13.5]
 7   0.9 ms   0.8 ms   0.9 ms  206.111.2.90.ptr.us.xo.net [206.111.2.90]
 8  22.7 ms  22.1 ms  23.5 ms  cr1.cgcil.ip.att.net [12.122.81.94]
 9  21.7 ms  21.8 ms  21.8 ms  cr1.cl2oh.ip.att.net [12.122.2.206]
10  22.3 ms  22.1 ms  21.9 ms  cr2.cl2oh.ip.att.net [12.122.2.126]
11  21.9 ms  21.7 ms  22.3 ms  cr2.phlpa.ip.att.net [12.122.2.210]
12  22.8 ms  22.9 ms  22.2 ms  cr1.wswdc.ip.att.net [12.122.4.54]
13  21.8 ms  21.6 ms  21.8 ms  cr83.wswdc.ip.att.net [12.123.10.110]
14  21.5 ms  21.7 ms  21.5 ms  12.122.135.1
15  22.7 ms  22.5 ms  22.7 ms  12-122-254-98.attens.net [12.122.254.98]
16  23.1 ms  22.6 ms  23.1 ms  mdf001c7613r0003-gig-10-1.wdc1.attens.net [63.240.193.10]
17   *        *        *       Request timed out.
18   *        *        *       Request timed out.
19   *        *        *       Request timed out.

NYC:

Code: Select all

C:\>tr 63.240.202.139

NFO win32 trace tool v2.04, copyright (c)2005 Nuclearfallout Enterprises, Inc.

Tracing route to 63.240.202.139 [63.240.202.139]
with up to 30 hops:

 1   0.3 ms   0.2 ms   0.2 ms  border2.ge2-13.nuclearfallout-45.ext1.nym.pnap.net [63.251.20.254]
 2   0.4 ms   0.4 ms   0.4 ms  core2.te6-2-bbnet2.nym007.pnap.net [216.52.95.89]
 3  63.3 ms   1.6 ms   0.6 ms  12.91.209.5
 4   7.8 ms   7.3 ms   8.1 ms  cr2.n54ny.ip.att.net [12.123.2.178]
 5   7.3 ms   6.2 ms   6.8 ms  cr2.wswdc.ip.att.net [12.122.3.38]
 6   7.1 ms   9.8 ms   6.5 ms  cr84.wswdc.ip.att.net [12.123.10.250]
 7   5.8 ms   5.8 ms   6.2 ms  12.122.134.1
 8   8.7 ms   8.4 ms   6.8 ms  12-122-254-98.attens.net [12.122.254.98]
 9   8.2 ms   8.3 ms   6.9 ms  mdf001c7613r0003-gig-10-1.wdc1.attens.net [63.240.193.10]
10   *        *        *       Request timed out.
11   *        *        *       Request timed out.
12   *        *        *       Request timed out.
13   *        *        *       Request timed out.
14   *        *        *       Request timed out.
15   *        *        *       Request timed out.
16   *        *        *       Request timed out.

This definitely smells like a ban/block of the entire IP space, but it could also be a routing mistake on their end. I've emailed support@battle.net on your behalf to see what they have to say about this.

Since Chicago and Dallas work, moving to one of these should fix your problem. To move your server, you can use a change order request from our order page here: https://www.nfoservers.com/order-virtua ... server.php

[Edge100x]

Blizzard was thoroughly unhelpful in their response to my inquiry about failed connections to their service and declined to investigate or elaborate.

From our perspective, it would seem that they just permanently ban whole IP blocks sometimes -- among them, a couple of ours. Quite possibly, this is in response to customers who have abused their service in the past, and they were too lazy to contact us with their concerns.

An actual end user might have more luck than I with them, if it's for a legitimate product. Posting in their forums also might bring more assistance.

[smeikle]

I haven't had too many negative dealings with the Blizzard support staff, so I would have to think that their lack of response is in fact due to the whole "previous users abusing services" issue.

Despite this, their inability to provide better communications to NFO(especially in the case of b2b) is quite pathetic from a cs/pr pov.

An actual end user might have more luck than I with them, if it's for a legitimate product. Posting in their forums also might bring more assistance.

He wants to install Stealthbot, which is a chatbot type tool that connects to Battle.net.

Not too sure if they would consider that a legitimate product, especially now with their RealID chat system in place (or whatever they are calling it).

[senkin]

Technically it is not a legit program since Blizzard are evil and don't let you use 3rd party programs without being in violation to End User Agreement.

I have tried on all versions of Windows Server. Also my windows server r2 in Chicago works, and yet my Senkin2 (which has the same issues as original poster) which is in InterNAP Dallas has the issue connecting.

I will try having it go from InterNAP Dallas to Chicago and test.