• Announcements

    • Budfred

      IE 11 copy/paste problem

      It has come to our attention that people using Internet Explorer 11 (IE 11) are having trouble with copy/paste to the forum. If you encounter this problem, using a different browser like Firefox or Chrome seems to get around the problem. We do not know what the problem is, but it seems to be specific to IE 11 and we are hopeful that Microsoft will eventually fix it.
    • Budfred

      PLEASE READ - Reversing upgrade   02/23/2017

      We have found that this new upgrade is somewhat of a disaster.  We are finding lots of glitches in being able to post and administer the forum.  Additionally, there are new costs associated with the upgrade that we simply cannot afford.  As a result, we have decided to reverse course and go back to the previous version of our software.  Since this will involve restoring it from a backup, we will lose posts that have been added since January 30 or possibly even some before that.    If you started a topic during that time, we urge you to make backups of your posts and you will need to start the topics over again after the change.  You can simply paste the copies of your posts that you created at that point.    If you joined the forum this month, you will need to re-register since your membership will be lost along with the posts.  Since you have a concealed password, we cannot simply restore your membership for you.   We are going to backup as much as we can so that it will reduce inconvenience for our members.  Unfortunately we cannot back everything up since much will be incompatible with the old version of our software.  We apologize for the confusion and regret the need to do this even though it is not viable to continue with this version of the software.   We plan to begin the process tomorrow evening and, if it goes smoothly, we shouldn't be offline for very long.  However, since we have not done this before, we are not sure how smoothly it will go.  We ask your patience as we proceed.   EDIT: I have asked our hosting service to do the restore at 9 PM Central time and it looks like it will go forward at that time.  Please prepare whatever you need to prepare so that we can restore your topics when the forum is stable again.
Sign in to follow this  
Followers 0
ifnotmewho

Production svr w/o network after HJT 010 LSP "fix"

2 posts in this topic

Windows 2000 Server, SP4, Primary use as a Terminal Server.

 

While using HJT to clean up some browser buttons, I sloppily fixed the following in HJT:

 

O10 - Broken Internet access because of LSP provider 'z:\windows\system32\rnr20.dll' missing.

 

 

HJT made no backup of the changes it made, and when complete, the network components of the OS were largely crippled:

- Pings IP addresses

- No DNS (nslookup fails)

- Netlogon service fails on boot (with the expected disastrous results)

 

And then came my most lovely discovery that since Veritas Backup Exec depends on the netlogon service, I'm going to have to work harder to get yesterday's registry back.

 

 

 

My question: can anyone give me some detail as to

- What this HJT check identifies when flagging this?

- What the "fix" portion does to it.

 

 

 

NOTE:

Already tried the following:

- lspfix (nothing appears either side)

- Removing and reinstalling the TCP/IP protocol

- winsockfix (same behavior, slight change in netlogon error messages)

 

 

Your input is greatly appreciated. Email away -- I'll be here until it's fixed.....

Share this post


Link to post
Share on other sites

Resolved, in case anyone was interested.

 

Cause: Never identified in detail, nor was the nature of the change caused by HJT. Generally, the cause was a breakdown in network communications that affected name resolution. Did not seem to be at TDI level, as sysinternals' TDIMon indicated success when networking attempts failed.

 

Resolution:

1. Uninstall all services, then protocols, from network adapters

2. Delete all registry keys associated with network protocols, and many services (winsock, winsock2,dhcp, lanman, others)

3. Reboot, and reinstall services then protocols again.

 

Boing! We're back.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  
Followers 0