seph ir oth
Mod'n Dat News Jon
- Reaction score
- 262
This has happened out of the blue ... kinda ... sorta.
So, I was playing Diablo II, and I got a temp ban. If you aren't familiar with temp bans in Diablo 2, if you switch characters too fast or make games too quickly you can get a temp ban, where you can connect to battle.net but it won't let you choose your character(s). A quick fix to this is to change your IP! So, I did an ipconfig/release and an ipconfig/renew in my command prompt (win 7 btw) and ... Suddenly I cannot connect to battle.net at all! See screenshot:
So, I've attempted to tracert to the USEast server and my route to their servers leave the Philadelphia area but ends in some NYC area ... see below (17th line of the tracert):
17 18 ms 27 ms 16 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
...Then it times out.
Anyone have any idea why it would suddenly NOT work? I have a dynamic IP setup: A modem is fed a cable, which feeds an ethernet connection to my router, then I connect wirelessly to that router.
NOTE: I've also tried clearing out the battle.net registry key in a last-hope attempt, as those are automatically generated if they dont exist upon connecting.
So, I was playing Diablo II, and I got a temp ban. If you aren't familiar with temp bans in Diablo 2, if you switch characters too fast or make games too quickly you can get a temp ban, where you can connect to battle.net but it won't let you choose your character(s). A quick fix to this is to change your IP! So, I did an ipconfig/release and an ipconfig/renew in my command prompt (win 7 btw) and ... Suddenly I cannot connect to battle.net at all! See screenshot:
So, I've attempted to tracert to the USEast server and my route to their servers leave the Philadelphia area but ends in some NYC area ... see below (17th line of the tracert):
17 18 ms 27 ms 16 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
...Then it times out.
Anyone have any idea why it would suddenly NOT work? I have a dynamic IP setup: A modem is fed a cable, which feeds an ethernet connection to my router, then I connect wirelessly to that router.
NOTE: I've also tried clearing out the battle.net registry key in a last-hope attempt, as those are automatically generated if they dont exist upon connecting.