Can't connect to Bnet with D2 LOD and 1.10 already installed

[Unregistered]

Title sums up a lot of the problem.
i have valid internet, using DSL with Bell South, ive made sure im not blocking connection to Bnet or D2 with a firewall.

I can sign on to every game I play and I used to play D2LOD all the time when 1.9 was out. I then quit playing for a long time and Ive just now decided to rejoin and check out 1.10.

I will be honest I used Pindlebot and maphack before during 1.9 but i deleted and uninstalled the hack programs and ive even installed/uninstalled the 1.10 patch a few times in hopes of being able to sign on. I've read the faq about siginging on to bnet and it says your account will only be banned for 2 days if found with hacks, ive tried signing on to all the servers, east, west, asia, europe, a few tims but all with no luck.

Its been about 2-3 months since ive played D2 and even had it installed for that matter, I uninstalled D2 durring 1.9 and all my hacks about 2-3 months ago.

So is there anything I can do about this or is it a lost cause?

 

[WinterNightPhantom]

When you try to connect to Battle.net with patch 1.10 installed, do you get an error message that says you got disconnected and you need to reconnect? And when you try to reconnect, you get the "Unable to connect to Battle.net..." error message? If so, that is a problem that I have seen before, although unfortunately I don't know of any definite solutions to it. It's a weird problem that has happened to some people who upgrade to patch 1.10, and one thing I noticed that was common to all of the cases was that apparently, the patch wasn't successfully applied, but the game still thinks that it's at version 1.10 and not 1.09.

Look for a file named "bnupdate.log" in your Diablo II directory and put its contents into your next post. I'd like to see what the patch log says.

If you don't get the disconnect error message when trying to connect with 1.10 and it just goes right to the "Unable to connect to Battle.net..." error message, that's different. I have a feeling that I know what might be causing that problem; I'd like you to post the contents of the "bnetlog.txt" file in your Diablo II directory in your next post as well. The connection log might tell us what the problem is, and it might be the one problem I've seen many times before where the person is trying to connect to 127.0.0.1 (a local loopback IP address) instead of a valid Battle.net server IP address. It indicates a corrupted server list, and the Battle.net server list in your registry can only be corrupted by hack and cheat programs.

If you haven't already, you should scan for trojan viruses with an up-to-date antivirus program. I wouldn't be surprised if those things you downloaded were trojan-infected.

 

[Unregistered]

Yes I am getting that error message, refers you to the tech forums.

The bnetupdate log says that the patch failed, I tried again 2 times and it failed both. I never looked at that before and my guess would be the patch is failing everytime. Good possibility it has somthing to do with an IP address.

I'm not infected, I have spybot and ran it again along with a norton scan before I downloaded another version of 1.10 and tried to install it.

Blizzard BNUpdate v2.72 compiled on Oct 16 2003
Log created at 6:47 pm on 02/26/2004

This patch upgrades Diablo II Lord of Destruction from version 1.07 or later to version 1.10.

NOTE: patch not required for file 'C:\Program Files\Diablo II\Game.exe' [version 1.0.10.39]

RESULT: Patch failed

Also, I followed the information on the tech forums and got a tracert repport that blizzard recomended. i am using bell south with home portal 2 way. The report said the destination was unreachabl. I'm not sure if I am trying to connect to 127.0.0.1.
I didn't see that in the tracert report. How could I find if I am trying to connect to that and if I am how could I change it?

 

[WinterNightPhantom]

You're getting the "You have been disconnected, please reconnect" error message or just the "Unable to connect to Battle.net..." error message?

Are you applying patch 1.10 from Battle.net, or are you applying the stand-alone version? If you haven't already, please uninstall the game, reinstall it and download and apply the stand-alone version. You can get it here:

http://www.blizzard.com/support/?id=mdt0387p

Umm... I don't think the fact that the patch install is failing has anything to do with an IP address. I'm not sure why the patch install is failing, but one possibility is that if you have an antivirus program running in the background, its "auto-protect" feature is preventing one or more game files from being properly modified. Before you patch, please disable Norton Antivirus (I'm assuming that's what you have) and close ALL other non-essential running processes. Go to your Windows Task Manager and close everything that isn't a Windows process.

Although you say that you're not infected, I wouldn't rule it out. If I were you, I would scan with these two other free scanners:

http://housecall.trendmicro.com
http://www.grisoft.com/us/us_dwnl_free.php

BTW, I don't think Spybot will find any trojans that you might have downloaded when you downloaded those things for Diablo II, as Spybot is designed to go after adware/spyware programs, not trojan viruses.

Where did you get this "other version" of Diablo II 1.10? You need to download and apply the official Blizzard patch, either from Battle.net or from the link I gave you.

The reason that the trace route said "destination unreachable" at the end is because Blizzard is now blocking ICMP packets from reaching their servers (ping and tracert packets). That message does not indicate whether or not you're trying to connect to 127.0.0.1. You will know if you're trying to connect to 127.0.0.1 or not if you look at the bnetlog.txt file. I'd like you to find it in your Diablo II directory, open it up and copy/paste its contents into your next post, please. If the log shows that you're trying to connect to that IP address, you will need to reset your Battle.net server list.

BTW, before the last time you reinstalled, did you delete the Diablo II directory off of your hard drive if it was there, just to make sure you've cleared out any remnants of your old installation?

Also, you said that you have posted on the tech forums... could you please link me to the thread you made so I can take a look at it?

EDIT:

I'm pretty sure that the reason you can't connect to Battle.net is that the patch install is not completing properly. We need to focus on getting it to complete properly, and then we'll determine if something else is causing the problem. I doubt the problem has anything to do with your Internet connection itself; in most cases it doesn't.

 

[Unregistered]

Yup had norton closed out when I was installing.
Got it from the official Blizzard site.

I didn't post on the tech forums though, I sent them an email telling them my problem and Iv'e read through the tech forums to see what info I can find. Most people who have this problem and the place where Blizzard refered me to in my Email response was this:

If you are having problems connecting to Battle.net or staying connected to
Battle.net, please try our easy to follow steps one at a time and then attempt
to connect to Battle.net, as each step has the potential of solving Battle.net
connection issues.

Step 1:
Check for Updates:

* If you are not able to get onto Battle.net, please download and install the
latest patch from the Patch page - ("http://www.blizzard.com/patches").
* If you have a router and are having various internet connection issues, please
check your router manufacturer's website for any updates.
* Check the Battle.net Status Forum -
("http://www.battle.net/forums/board.aspx?ForumName=battlenet-status") for any
information regarding server maintenance.
* Check the Technical Support News Page - ("http://www.blizzard.com/support/")
for any information about current connection issues.

Step 2:
Temporary Restrictions:
Please try to connect to all four Battle.net Realms (USEast, USWest, Europe, and
Asia). If only one Battle.net Realm is inaccessible to you, then it may just be
a temporary connection problem or a temporary restriction. Battle.net access may
be restricted (up to 1-2 days) for one of the following reasons:

* Spamming text in the chat channel (often associated with bots)
* Rapidly connecting/disconnecting to Battle.net (often associated with bots)
* Repeated attempts to use an invalid CD-Key
* Repeated use of an incorrect password may lock an account login for your
protection
* Repeated use of third-party programs (hacks) - these include but are not
limited to sending bad packets, flooding the server(s), and the use of hack
programs

Step 3:
Battle.net Server List:
Someone or something may have modified your server list so you are no longer
connecting to a Blizzard Entertainment Battle.net server. For instructions on
restoring the correct server list, please go to this page -
("http://www.blizzard.com/support/?id=aInformation0633p1").

Step 4:
Internet connection notes:

Firewalls, Routers, and Internet Connection Sharing

* If you are using any type of firewall, router, or you are sharing your
internet connection between several computers, you may need to set your system
up to allow access to Battle.net. For instructions on setting up your
connection, please go to this page -
("http://www.blizzard.com/support/?id=msi0423p").

Test your Internet connection:

* Use the Telnet command to make sure your Internet connection is running
smoothly. Go here for more information -
("http://www.blizzard.com/support/?id=adt0631p").
* Use the Trace Route report to help identify if and where a problem is
happening. Go here for more information -
("http://www.blizzard.com/support/?id=adt0631p2").
* Use the NSLookUp command to check the connection. Go here for more information
- ("http://www.blizzard.com/support/?id=adt0631p3").


Step 5:
Parental Controls and Dial-Up Users:

Parental Controls:

* To connect to Battle.net via Dial-up, make sure you are running the latest
version of your internet service's software. You can usually update the latest
version from your internet service's website.
* Make sure you are connecting to the internet with Parental Controls turned
off. If you continue to experience problems, try logging onto the internet using
the Main Account. You can also try connecting to internet using a different
local access number if your internet service offers this feature.

Dial-Up Users:

* Wait 15 minutes to an hour and try connecting to Battle.net again. Many
Internet connection issues are temporary and will clear up on their own.
* Your modem may need updated drivers to work more reliably. Check your modem
manufacturer's website for updated drivers, or contact them by phone.
* Try different dial up numbers for your Internet Service Provider if alternate
numbers are available in your area.


Additional information for Macintosh Dial-Up Users:

* Your modem script may need changes to work with your modem more reliably. Your
ISP or Apple should be able to provide assistance with changes to your modem
script.
* You may need to update your version of Open Transport. The Open Transport
software updates are available on the Software Updates area of Apple's web site
- ("http://www.apple.com/").

It's the regular information everyone gets with this problem and most people with my same problem on the tech forums at Blizzard seem to not have any luck.

 

[WinterNightPhantom]

Did you close ALL running background programs before you patched, including Norton?

You still haven't answered the following question, and I'd like you to answer it please... when you try to connect to Battle.net with 1.10, do you get an error message saying that you've been disconnected and that you need to reconnect?

So you've tried the stand-alone patch and there was no difference?

Could you please apply patch 1.10, try to connect to Battle.net again and then post the contents of the bnetlog.txt file in your Diablo II directory?

Sorry if I seem like I'm trying to be a pain by repeating all these questions, but it's important that you answer them.

I'm familiar with the usual response Blizzard gives via e-mail and on the Battle.net support forum to people who can't connect to Battle.net with Diablo II, and I don't think that any of the steps you got will help you. Like I've said before, I don't think this is a connection problem, I think it's a matter of the 1.10 patch not being applied properly.

I'm trying to think of why the patch isn't being applied properly, and my best guess is that it has something to do with the fact that you used those hack programs. Earlier I had asked if you had deleted the Diablo II directory off of your hard drive if it was there before you reinstalled and patched, and that's because I wanted to make sure that you weren't bringing anything from your previous installation in.

If you're using Windows 2000 or XP and you're patching under a Limited user account, try logging on as an Administrator and then patching. I would also check your hard disk for errors with Windows Scandisk or an equivalent program.