+- The Lurker Lounge Forums (https://www.lurkerlounge.com/forums)
+-- Forum: Lurker Games (https://www.lurkerlounge.com/forums/forum-6.html)
+--- Forum: Diablo II (https://www.lurkerlounge.com/forums/forum-8.html)
+--- Thread: Nothing is ever easy (/thread-10026.html)
Nothing is ever easy - ShadowHM - 10-28-2003
Hi
I am baffled and confused.
All of a sudden, I cannot join or make Realm games. I played earlier today, and all was fine. But now......
I can make a SP game.
I can make a TCP/IP game. I can even have someone join that game.
I can join an Open Bnet game.
But I cannot get into a Realm game. Just as the loading screen starts to open the portal, I hear a little hammer sound and the screen freezes. The same goes for making Realm games.
I have re-booted numerous times. I have run the game through D2 Accelerator and not. I have disabled most of the start-up menu, so as to not clog up RAM.
I am out of ideas for what to try next.
Anyone have advice/suggestions?
Nothing is ever easy - Celester - 10-28-2003
Hey, first time post, longtime lurker (cliche my first post!:D) but what I checked was that useast.battle.net wasn't pingable (request timed out) and trying to tracert to useast.battle.net can't be done. However, I did tracert through 63.240.202.134
What I can get from this is that the DNS server for useast.battle.net has gone down.
Here's the results I got:
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Celery>ping useast.battle.net
Pinging useast.battle.net [63.240.202.134] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 63.240.202.134:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Here is where I tried to ping it through the DNS
C:\Documents and Settings\Celery>tracert usest.battle.net
Unable to resolve target system name usest.battle.net.
C:\Documents and Settings\Celery>tracert 63.240.202.134
Tracing route to 63.240.202.134 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.0.1
2 12 ms 11 ms 11 ms xxx.xxx.xxx.xxx <-my cable modem address.
3 16 ms 12 ms 20 ms halaswitch1.cgocable.net [24.226.5.1]
4 12 ms 35 ms 53 ms d226-5-250.home.cgocable.net [24.226.5.250]
5 22 ms 27 ms 42 ms cgowave-0-121.cgocable.net [24.226.0.121]
6 31 ms 12 ms 37 ms ra1sh-pos7-1.mt.bigpipeinc.com [66.244.223.225]
7 25 ms 19 ms 19 ms rc2sh-ge9-0.mt.shawcable.net [66.163.66.17]
8 26 ms 28 ms 62 ms rc1ch-pos7-0.il.shawcable.net [66.163.77.14]
9 25 ms 34 ms 26 ms rc2ch-pos2-0.il.shawcable.net [66.163.65.2]
10 27 ms 24 ms 26 ms ge-1-2-0.r02.chcgil01.us.bb.verio.net [129.250.10.153]
11 34 ms 25 ms 27 ms p16-3-0-0.r00.chcgil06.us.bb.verio.net [129.250.5.114]
12 47 ms 26 ms 39 ms agns-gw.sffca.ip.att.net [192.205.32.193]
13 27 ms 25 ms 57 ms tbr1-p010401.cgcil.ip.att.net [12.123.6.66]
14 42 ms 60 ms 49 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
15 55 ms 43 ms 46 ms tbr2-p012501.n54ny.ip.att.net [12.122.9.130]
16 59 ms 57 ms 69 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.54]
17 48 ms 45 ms 46 ms gbr6-p40.wswdc.ip.att.net [12.122.11.190]
18 43 ms 44 ms 54 ms gar3-p370.wswdc.ip.att.net [12.123.9.69]
19 45 ms 46 ms 68 ms mdf1-gsr12-1-pos-7-0.wdc1.attens.net [12.122.255.182]
20 45 ms 76 ms 56 ms mdf1-bi8k-1-eth-1-1.wdc1.attens.net [63.240.192.246]
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.
Hope that helps a bit.
Nothing is ever easy - Archon_Wing - 10-28-2003
Ok, so you can actualy log on to battle.net and the chat screen right?
Well, B.net has a tendency to do that to you. Try joining a random public game. If you can't join any of the games on the list, come back here and I'll think a little bit more. :)
Nothing is ever easy - Archon_Wing - 10-28-2003
Blizzard has disabled ping/tracert for battle.net while ago. That's why. :)
Nothing is ever easy - Celester - 10-28-2003
Well, that does seem to explain that.
I haven't been on bnet in ages, mostly single player. That explains a whole bunch though.
Nothing is ever easy - ShadowHM - 10-28-2003
I did my first testing all with one character on the Realm (the SP/Open characters were different ones, of course).
After an errand where I could think some more as I drove, I tried this:
I deleted the bnet cache and the USEast folder in the D2 folder and then logged onto USEast again.
I still could not join or make a game with the one character. But I could with a new baby char on that account, and the baby could join games and make games.
So I went back to the character that had the problem. He could still join Bnet, still join a channel, but the game still froze when he either tried to enter a game or make a game.
Any further ideas?
Nothing is ever easy - Archon_Wing - 10-28-2003
Ahh, so it's only confined to one character? Well, I can really guess it's really b.net's fault. Their server thinks that your character has joined a game when it really hasn't. I have encountered this problem before. This should resolve itself in a few hours.
P.S. Battle.net has been turbulent to say the best. I get a lot of server down lately.
Nothing is ever easy - Occhidiangela - 10-28-2003
Or did you just install cable modem?
Might need to open ports 6112 and one of the 4000 series, I forget which.
Nothing is ever easy - Casperi - 10-28-2003
According to the battle.net status forum, the realm is to be down from 17:00 to 19:00 GMT today for maintenance. I think that's noon-2:00 est. Try again in a couple hours?