Does Diablo 1 battle net works now? (not specific in VB)

[jugns271]

I've installed diablo 1 in XP guest OS and patched to latest 1.09b...

I've set default windows firewall let the diablo.exe connect internet..

After run the game when I select battle.net and shows follow message and no response.. I must

click cancel.. (in Host XP firewall set the VirtualBox can connect internet already)



But this is not a VB specific problem..

I've installed Diablo 1 in Host OS (XP) too and samely I can't connect battle.net



I've tried other 4 gateways and the same..

I think blizzard have discontinued supporting Diablo1 for playing Battle.net..

Is there anyone playing Diablo 1 battle.net in any OS(virtual OS or Real OS) now?

[Sasquatch]

You're better off asking this on the Blizzard forums instead of here. We don't have any influence at Blizzard shutting down a service for a very old game.

[squall leonhart]

hes not asking about that, hes asking if the connection to Bnet works through Vbox, which if his network is configured properly it would.

the reason Starcraft works through vbox is because the recent updates have enabled upnp port mapping support.

[Sasquatch]

hes not asking about that, hes asking if the connection to Bnet works through Vbox, which if his network is configured properly it would.

the reason Starcraft works through vbox is because the recent updates have enabled upnp port mapping support.

Check is post again:

I've installed Diablo 1 in Host OS (XP) too and samely I can't connect battle.net

His Host doesn't work either. He even says it's not VB specific. What more info do you need to call off-topic here?

[squall leonhart]

I read his post just fine, Again, this has nothing to do with blizzard shutting down servers, and again, if his diablo and network was properly was configured to forward the required port it would work just fine.

http://us.blizzard.com/support/article. ... leId=20832
http://portforward.com/cportsnotes/batt ... tlenet.htm

[Sasquatch]

Which, again, is not ours to discuss here. When the Host is showing the same problem as the Guest, VB is out of the equation.

The problem has been found, so to avoid further senseless discussion, I'm locking this thread.