Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ishinozaki]

Hello,

I recently bought a DIR-655 for 6,000 PHP (~140USD); just about two days ago.

I was distressed all night configuring it to let me login to Starcraft II Southeast Asia region (sea.battle.net). I have tried all forms of NAT, disabled SPI and other ridiculous settings. I did a DMZ as my last resort, STILL NO LUCK!

The DIR-655 came with 1.30WW and I recently upgraded it to 1.34NA. (it still wouldn't work with 1.30WW)... and I also noticed the USB 3G Adapter support was dropped.

How can I fix this? Clearly something is wrong. Once I've set my NAT I always made sure to use a port scanner to see if 1119-1120 (SCII's ports) are open. It doesn't make sense why it wouldn't work with DMZ either!

It's connected to an ADSL modem that's bridged.. to make sure it's not just my internet connection I connected my modem straight to my machine and used it for PPP and I was able to login and play just fine. It's good to note that I'm stuck in the login screen where you provide your password, it's good to note that the game will give an error message if I provide the wrong password yet won't allow me to proceed any further than tht, even the part where I see my IGN/avatar.

Please help.

Thanks a lot.

[ishinozaki]

Additionally, I am unable to ping "sea.battle.net" (game servers).... always times out.

[ishinozaki]

After Googling "dir-655 battle net":

http://forums.worldofwarcraft.com/thread.html?topicId=18031200373&sid=1
(Player reporting he cannot stay online for more than five minutes on this router)

[ishinozaki]

Tracert gives me:

Tracing route to sea.battle.net [202.9.66.38]
over a maximum of 30 hops:

  1    35 ms    36 ms    35 ms  120.28.187.1
  2    35 ms    35 ms    35 ms  10.109.9.53
  3    36 ms    35 ms    35 ms  120.28.0.181
  4    36 ms    36 ms    35 ms  120.28.0.6
  5    40 ms    35 ms    42 ms  120.28.0.74
  6   107 ms   106 ms   122 ms  203.117.5.89
  7   109 ms   106 ms   106 ms  an-ats-int10.starhub.net.sg [203.118.3.176]
  8   120 ms   167 ms   119 ms  203.116.5.146
  9   127 ms   123 ms   124 ms  csw305-br602.sgw.equinix.com [202.79.192.190]
 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     *        *

[EddieZ]

1. lookup the definitiion of 'bug'
2. change the title of this topic

The trace you show us blames your ISP. Sorry, but user routers do not mess up ISP operation.

[ishinozaki]

"to make sure it's not just my internet connection I connected my modem straight to my machine and used it for PPP and I was able to login and play just fine."

Read that. Either way using the modem as a PPP gateway --I can play just fine. It's the modem. Wasn't that obvious when I DMZ'd my machine and I still couldn't connect?

[ddaniel51]

Hi Ishi

For your information a ping to sea.battle.net from Arizona USA fails at the same point as yours.

sea.battle.net is not responding to pings.

Good luck.

[ishinozaki]

Thank you Daniel, I was able to verify that through my friend as well. It seems odd that even DMZ won't get me to login, but again, if I enter a wrong password, it'll prompt me.

[EddieZ]

"to make sure it's not just my internet connection I connected my modem straight to my machine and used it for PPP and I was able to login and play just fine."

Read that. Either way using the modem as a PPP gateway --I can play just fine. It's the modem. Wasn't that obvious when I DMZ'd my machine and I still couldn't connect?

Not when you posted the trace info which says otherwise.

Did you already adjust the 655 firewall settings? Default is very strict.

[Cobra]

Have you looked at Blizzard?

Are you unable to connect to Battle.net and you are using a firewall, router, or proxy?

[ishinozaki]

Thanks for the reply.

No firewall aside from the one built-in Windows, proxy too. Basically if I connect directly using my modem or use another connection (3G USB modems) I can connect just fine, it's just when I use the 655.

Yup I've tried all possible firewall tweaks and none of them worked..

Returning my unit tomorrow to see if it's a batch defect but if the store allows it I'm upgrading it to a Linksys 610N.

[EddieZ]

Thanks for the reply.

No firewall aside from the one built-in Windows, proxy too. Basically if I connect directly using my modem or use another connection (3G USB modems) I can connect just fine, it's just when I use the 655.

Yup I've tried all possible firewall tweaks and none of them worked..

Returning my unit tomorrow to see if it's a batch defect but if the store allows it I'm upgrading it to a Linksys 610N.

You need to configure the Windows firewall, I guess you picked that up from the article...

[ishinozaki]

Thanks EddieZ, I have configured it, I even tried it off..

Problem solved... solution.... replaced it with Linksys WRT610N.

Thank you very much for your replies, much appreciated.