Cannot backup rasmans.dll

Using XP Home, SP2, and XP backup program, backup always fails to backup rasmans.dll. The file version of rasmans.dll I have is 177kb dated 6/22/06. Any help? Thanks, Mike.

 

Hi Washingtondude, I've just Googled your Rasmans.dll and there is reference there to a security problem and need to verify whether it is a genuine .dll I would suggest you go to Windows Support and make a check or just wait for someone more experienced to help. Neil.
I note it was a Remote Network Connection.dll.

 

Hi retiredlearner: Yes, I've been chasing Google hits for over an hour now and I can't get a definitive answer for a fix. Rasmans.dll is part of a network connection manager I gather, and since I use my network card to connect via dsl I'm loathe to just delete or replace the file. But, thanks for the input and maybe someone'll know the fix. Cheers, Mike

 

Hi, washingtondude. Welcome to Windows BBS!

I'm sorry I don't have an immediate fix for your issue but I am still investigating.

Out of curiosity, exactly where is the particular "6/22/06" rasmans.dll file you cannot back-up located? (That file name is in several locations and it might help us to know what the path to the troublesome one is.) Given your stated experience level, I am assuming you're familiar with searching your hard drive for file names (including hidden files and folders). If not, just let us know and we will help you with that.

If you can provide additional details about your "6/22/06" rasmans.dll file (such as the MD5/SHA-1 hash values, for example), those details might also help us resolve your issue. (Karen's Hasher is a handy free utility for calculating hash values.)

While I was researching your issue last night, I discovered some discrepancies regarding the rasmans.dll files on my own computer. Here's a link to that thread in the off-chance the information might become helpful for resolving your issue. It also will give you a hint about why I am particularly interested in your stated file date.

 

Thanks, Mailman: The file is located in Windows/System32. Note there are two (2) "rasman" files, one with a singular name and one with a plural name. The one spelled "rasman.dll" is not the problem. The one spelled "rasmans.dll" is the one failing backup every time. Here Karen's Hasher results: (read error in both cases) (seeing failures on the SHA-1 and MD5 algos, I tried the rest of them with the same results)

Karen's Hasher v2.3
http://www.karenware.com

Date: 6/24/2007 4:44:19 PM
Computer: YOUR-FD6NVJCER4
User: Michael Langford

Files Hashed: 1

File Name SHA-1 Hash
C:\WINDOWS\system32\rasmans.dll ** Not Computed **
Karen's Hasher v2.3
http://www.karenware.com

Date: 6/24/2007 4:47:31 PM
Computer: YOUR-FD6NVJCER4
User: Michael Langford

Files Hashed: 1

File Name MD5 Hash SHA-1 Hash
C:\WINDOWS\system32\rasmans.dll ** Not Computed ** ** Not Computed **

__________

Addtionally I searched for "rasman" and it occurs in these places/variations:

rasman.dl_ \Windows\I386
rasmans.dl_ \Windows\I386
rasman.dll \Windows\system32
rasmans.dll \Windows\system32
rasman.dll \Windows\ServicePackFiles\i386
rasmans.dll \Windows\ServicePackFiles\i386

Thank you for helping. Mike

 

Hmmm... That's strange. I have never experienced a ** Not Computed ** result with Karen's Hasher. Have you tried Hasher on a non-system file (such as a text file somewhere else on your hard drive) and got the same result?

I downloaded version 2.3 and installed it (over the top of v2.2.1) and successfully computed an SHA-1 hash for the C:\WINDOWS\system32\rasmans.dll file. Therefore, it doesn't appear to be a glaring error with Karen's v2.3 release.

This is puzzling. Perhaps someone who is familiar with your Hasher problem will jump into the discussion.

I'll do some poking around to see what I might dig up.


In the meantime, please navigate to your C:\WINDOWS\system32\rasmans.dll, right-click on file name, and select "Properties ". Please give us the following info.

• Under the "General" tab:
  • "Size:" (exact # of bytes)
  • "Created:" date (including the exact time)
  • "Modified:" date (including the exact time)
• Under the "Version" tab, in the "Other version information" section:
  • "File Version" Value: (including the info in parentheses)

 

Thanks for your time. I did successfully run the hasher on "rasman.dll" so I'm guessing the other file is corrupt or infected. Here are the specs you requested:

file size 184,320
created date Thursday, June 22, 2006, 5:59:17 AM
modified date Thursday, June 22, 2006, 5:47:18 AM
There is no version tab in the prop window. The summary tab info is blank.

Mike

 

You're very welcome. Thanks for the file info. I'm glad your Hasher is working properly. Looks like we're making progress!

First, let's see if the file is infected.

Please upload the troublesome rasmans.dll file to Jotti's Online Scan for analysis. The scan will take a few minutes as several applications are used.

If any malware is detected,

• please drag your mouse across the results (after the scan is complete) so all of the report text is highlighted.
• Right-click on the highlighted text and select "Copy ".
• Then open a reply here and right-click in the message edit section and select "Paste ".

If the file is infected, then ignore my instructions below (for now) because we will need to take certain steps to seek malware removal help.

============

If the file appears clean or corrupted, then perhaps Windows XP's System File Checker (SFC) will help you resolve your issue. (Here are my canned instructions. )

• Have your Windows XP CD handy because you may be prompted to insert it into your CD drive during this process.
• Click Start > Run...
• Type [FONT= "Courier New"][SIZE= "3"]sfc /scannow[/SIZE][/FONT] in the "Open:" field.
• Click the OK button.

A "Windows File Protection" window will open and display its progress. If SFC runs successfully without any intervention from you, it will take approximately 15-25 minutes to complete. When SFC completes, the "Windows File Protection" window will simply disappear.

To see any changes that may have been made by SFC after it completes:

• Click Start > Run...
• Type [FONT= "Courier New"][SIZE= "3"]eventvwr.msc[/SIZE][/FONT] in the "Open:" field.
• Click the OK button.
• Click the "System" item on the left side of the "Event Viewer" window.

Any changes made by SFC will be displayed (in reverse order) as "Windows File Protection" events between Event ID 64016 (Windows File Protection started) and 64017 (Windows File Protection completed).

Double-click on an event (or right-click on the event and select "Properties ") to view details about the event. You can use the up/down arrow buttons on the right side of the event's "Properties" window to view details about adjacent events without having to close the event's "Properties" window.

If you want to copy event details to your clipboard (for pasting into Notepad or a forum message, for example), use the button immediately below the up/down arrow buttons in the event's "Properties" window.

 

There were 34 events and all but one of them indicated a bad hard disk block
"The device, \Device\Harddisk0\D, has a bad block. "

There was one sr event and the description was:
"The System Restore filter encountered the unexpected error '0xC0000006' while processing the file 'rasmans.dll' on the volume 'HarddiskVolume1'. It has stopped monitoring the volume. "

There were no viruses detected at Jotti's.

I do have Spinrite so I can start that and let it run for several hours if you think that'll fix it. Thanks for your time. Mike

 

Additionally I took another look at the file properties of rasmans.dll and now there is a version tab where there wasn't before (don't know what to make of that, and yes, I've had my coffee already ). Version # 5.1.2600.2936 (xpsp_sp2_gdr.060621-2347) Mike

 

I've been following this thread with interest and have learned a few things in the process - Thank you.

Now for my 2¢ ...........

SpinRite is a very good tool but I would caution you to make removable media backups af all critical data ASAP. Quite often, this condition is indicative of an impending catastrophic hard disc failure. With the cost of HDDs these days, you may be best served by replacing instead of repairing.

 

Thanks, Rockster! You jumped in at exactly the right time!

 

Thank you both for your help and advice. Indeed, Spinrite is forecasting doom and gloom. I did make an external hd backup yesterday so if I lose c: the only thing I'll lose is today's emails. I ran Spinrite in it's fastest mode and it reported one sector as unrecoverable.

Additionally, I just copied rasmans.dll to a different name, renamed both and the copied file passes the hash test so my thinking is there is indeed a bad spot on my drive though I can't begin to understand why a copy would be able to read the file and move it and nothing else will read it to this point.

I'm going to be out for a few hours so I'm going to run Spinrite again and see if it'll fix things up. Cheers, Mike