Hi Support Team,
I Cannnot log in to Diablo 2 from my home internet since yesterday,
It Just Keep stuck at below screen:
CHECKING VERSIONS…
and then it says:
Battle.net not responding…
trieded for nearly 24 hours still remaining the same,
althought I’m able to use my Hpone hotspot to play,
so im pretty sure my account is not ban or anything,
need help and my mobile data cost heaps .
atleaste give me a timefame when will this be fix.
Many thanks
Hey, Hydeist. I’m not seeing any issues with a temporary restriction here, so it should be good there. It looks like it is currently in use now, are you still experiencing issues?
Could you provide a traceroute and pathping test while on the home network connection? Copy and paste the text file created and paste it between two ~~~ like so:
~~~
Tracert and Pathping Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
Hi Caterpepi,
yeah I was using my Hotspot(mobile data) to play,
just now i tried again switching it back to my home internet,
it goes to CHECKING VERSIONS…
then
Battle.net not responding.
Pleasr Try Connetiong again in a few minutes.
TRACERT:
Tracing route to uswest.battle.net123456 [12.129.236.19]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms MyGateway.Home [192.168.0.1]
2 5 ms 5 ms 4 ms meb2-l101.bng.optusnet.com.au [175.33.0.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 20 ms 17 ms 18 ms mas1-hu0-4-0.ig.optusnet.com.au [198.142.249.242]
6 171 ms 172 ms 171 ms 203.208.131.205
7 * * * Request timed out.
8 * * * Request timed out.
9 174 ms 182 ms 171 ms ae14.mpr1.lax12.us.zip.zayo.com123456 [64.125.27.39]
10 188 ms 215 ms 174 ms zayo-att.lax12.us.zip.zayo.com123456 [64.125.12.154]
11 183 ms 180 ms 174 ms cr1.la2ca.ip.att.net123456 [12.122.128.98]
12 176 ms 198 ms 178 ms gar5.lsrca.ip.att.net123456 [12.122.128.53]
13 178 ms 175 ms 176 ms 32.130.250.2
14 173 ms 177 ms 212 ms 32.130.250.15
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Pathping:
Tracing route to uswest.battle.net123456 [12.129.236.19]
over a maximum of 30 hops:
0 DESKTOP-PDT51BC.Home [192.168.0.3]
1 MyGateway.Home [192.168.0.1]
2 meb2-l101.bng.optusnet.com.au [175.33.0.1]
3 * * *
Computing statistics for 50 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-PDT51BC.Home [192.168.0.3]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% MyGateway.Home [192.168.0.1]
0/ 100 = 0% |
2 5ms 0/ 100 = 0% 0/ 100 = 0% meb2-l101.bng.optusnet.com.au [175.33.0.1]
Trace complete.
please help.
Many thx
Hydeist,
We do see the temporary restriction on your home IP. It looks like the restriction may have had to do with VPN usage or a modified game client. This link has a list of the most common possibilities.
The restriction on your home IP will fall off on the afternoon of August 31st. In the mean time you can use your hotspot to play if you wish.
Thankyou so much Drakuloth,
I’ll try to find out what casue this VPN thing.
because i dun vpn at all.
once again thankyou support teams.