|
|
 |
|
|
Pages: 1
Cannot connect to battle.net as a LAN user
(Click here to view the original thread with full colors/images)
Posted by: blogworm
I am a LAN user, and cannot connect to battle.net now. When I tried "telnet asia.battle.net 6112" cmd only to get error message. So I think the needed ports are closed. Then I tried sockscap(127.0.0.1:1080 as socks proxy)+socks2http, but still cannot access my a/c after connectting to the server. The bnetlog.txt informaion is:
6/15 19:34:27.514 Connecting to Battle.net...
6/15 19:34:27.725 querying gateway asia.battle.net
6/15 19:34:27.905 searching for the fastest server
6/15 19:34:31.750 Connected to server 211.233.0.51
6/15 19:34:31.760 accessing accounts
I wonder it is possible to use sockscap+socks2http to bypass the firewall, and do I still need to find another valid socks proxy other than 127.0.0.1:1080? If the bnetlog.txt informaion means I have sucessfully connected to the server, why I still cannot access my a/c?
Posted by: NegotiatorSmith
If you can't connect with Telnet, that's why you can't connect with Diablo II, even though bnetlog.txt seems to indicate otherwise. What error did you get with Telnet?
I'm honestly not familiar with sockscap and such, but if you're on a LAN and port 6112 TCP outbound is being blocked, there's probably a reason for that.
|
|
|
|
|
