| Network shares issue (after getting over an infection) 
This is the message every computer and device gets when trying to connect to my computer's network shares at that address (or any network shares links).
A few days ago I got over a ZeroAcccess rootkit infection (yes it is really gone, I made sure with SuperAntiSpyware, HijackThis, Spybot Search and Destroy, Malwarebytes Anti-Malware, CCleaner, the Kaspersky Rescue Disk, ComboFix, TDSSKiller, GMER, rkill, and UnhackMe). Ever since, I can connect to anyone else and nothing else seems affected.
We're all running Windows 7, and for the purposes of tracking down the cause I have disabled anything that could be preventing the connection (firewalls, anti-viruses, or anti- adware/spyware, as well as the native protections of Windows Firewall, Security Center, and Windows Defender).
(I have restarted my computer after every one of these steps.)
• I have tried leaving and rejoining the workgroup
• Deleted and re-added my shares
• Deleted and re-added the permissions on my shares
• Have checked various registry entries (I really think it might be the issue, not sure why)
To be clear, there is no other issue than the other computers in the house connecting to (or seeing) my shares. I don't know if the it is left over settings from the rootkit or something from one of the anti-spyware softwares I ran (like Spybot's immunize or the like).
Any help would be appreciated. |
|
tomdlgns
join:2003-03-21
Chicago, IL
kudos:1 | can you ping hp-pc?
do you know the ip if hp-pc?
try \\ip-address
also, if you can't ping it by hostname, try to ping it by IP address. |
|
 mozerdLight Will Pierce The DarknessPremium,MVM
join:2004-04-23
Nepean, ON
1 edit | reply to guest2
On each Windows 7 computer in your network make sure to
Enable network discovery
THEN
use the Windows 7 built-in tool that may be able to solve your issue:
[a] Choose Start¨Control Panel¨Network and Sharing Center.
[b] Click Troubleshoot Problems
[c] Click Shared Folders
Then follow the prompts and see where it takes you.
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
|
| reply to tomdlgns
said by tomdlgns:can you ping hp-pc?
do you know the ip if hp-pc?
try \\ip-address
also, if you can't ping it by hostname, try to ping it by IP address.
Browsing by IP does not work either. |
|
|
|
tomdlgns
join:2003-03-21
Chicago, IL
kudos:1 | can you ping by ip or host name? |
|
| said by tomdlgns:can you ping by ip or host name?
No, all packets dropped. |
|
1 edit | reply to mozerd
said by mozerd:On each Windows 7 computer in your network make sure to
Enable network discovery
THEN
use the Windows 7 built-in tool that may be able to solve your issue:
[a] Choose Start¨Control Panel¨Network and Sharing Center.
[b] Click Troubleshoot Problems
[c] Click Shared Folders
Then follow the prompts and see where it takes you.
I ran the troubleshooter for Incoming connections for both "see this computer" and "share files", and Shared Folders/HomeGroup (even though I have no outbound issues), all with "Ally repairs automatically" checked to no avail.
Also, network discovery is set to ON. |
|
| reply to guest2
is this network share available to admin and users or just admin? |
|
1 edit | said by medbuyer:is this network share available to admin and users or just admin?
I set the permissions to "Everyone" (and allowed all access). |
|
| reply to guest2
Just wanted to note that a week ago (prior to my infection) I had no issues ever with my shares. My Wii and all the computers in the house used to connect to my shares daily. |
|
mozerdLight Will Pierce The DarknessPremium,MVM
join:2004-04-23
Nepean, ON
1 edit | said by guest2:Just wanted to note that a week ago (prior to my infection) I had no issues ever with my shares. My Wii and all the computers in the house used to connect to my shares daily.
I would suggest that you try System Restore ... Pick a date that precedes your rootkit infection by 14 days ... If system restore does not solve your issue then you can try a special way of doing Windows Repair and if that does not solve the issue you will need to reinstall the OS.
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
|
| reply to guest2
|
|
| reply to guest2
said by guest2:said by tomdlgns:can you ping by ip or host name?
No, all packets dropped. you MUST start here before you do ANYTHING else. you HAVE to establish that the device can at LEAST be pinged.
first, disable all firewall/security software to test. if you still can't be pinged by IP, you're in a world of hurt.
if you're able to get pinged by IP, then see if you can be pinged by the netbios name, and then move forward with figuring out if shares can be accessed. |
|
| said by mozerd:said by guest2:Just wanted to note that a week ago (prior to my infection) I had no issues ever with my shares. My Wii and all the computers in the house used to connect to my shares daily.
I would suggest that you try System Restore ... Pick a date that precedes your rootkit infection by 14 days ... If system restore does not solve your issue then you can try a special way of doing Windows Repair and if that does not solve the issue you will need to reinstall the OS. Were it that easy. Alas, system restore is not an option. With this “in place upgrade” will I lose my current user and system settings? (I did not see anything about it in the link but it seems likely) If so, that seems a bit extreme for what may be a simple registry entry. Not sure why I am partial to the idea it might be a registry issue, but any thoughts on repairing network issues along that route? I took a look, and they all speak of a current infection, which is no longer the case. said by AngryBlakMan:said by guest2:said by tomdlgns:can you ping by ip or host name?
No, all packets dropped. you MUST start here before you do ANYTHING else. you HAVE to establish that the device can at LEAST be pinged. first, disable all firewall/security software to test. if you still can't be pinged by IP, you're in a world of hurt. if you're able to get pinged by IP, then see if you can be pinged by the netbios name, and then move forward with figuring out if shares can be accessed. The IP comes back with 4 timeouts and the netbios ping finds nothing to ping. As I mentioned, there is no firewall or security software running. |
|
| said by guest2:I took a look, and they all speak of a current infection, which is no longer the case.
you need to read the whole thing...
accdg. to what I read, the infection somehow destroys this one file thats attached to networking and its related registry entries and that their internet connection and LAN are not working right..
some have taken the steps including downloading this one application that supposedly fixes that broken connection. |
|
mozerdLight Will Pierce The DarknessPremium,MVM
join:2004-04-23
Nepean, ON | reply to guest2
said by guest2:With this “in place upgrade” will I lose my current user and system settings? (I did not see anything about it in the link but it seems likely) If so, that seems a bit extreme for what may be a simple registry entry.
Not sure why I am partial to the idea it might be a registry issue, but any thoughts on repairing network issues along that route? The in-place upgrade will not destroy any existing data ... It will replace all the OS files. The root kit destroyed files related to network issues and probably many more important OS files .. So a registry fix is not the way to go.
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
|
| reply to guest2
said by guest2:The IP comes back with 4 timeouts and the netbios ping finds nothing to ping. if you can't ping by IP, netbios checking is a waste of time in all cases.
go to services.msc in run. is the "server" service started? if not, try and start it. if it doesn't start, what error did you get? |
|
| reply to guest2
Angry Blank Man is correct.
You must first resolve your network issue before you will be able to fix your share access issue.
Be sure your server can ping the gateway or router.
Be sure your server can ping the machines trying to connect to it.
Make sure the connect and activity lights are on the switch etc.
We had some power issues recently and we use a Thecus 5200 nas box for storage.
After the the power issues I could see all of the windows servers but not the nas box.
Panicked and rebooted the box, it said it was fine and reported the right ip address, rebooted the switch, nada. Then noticed I can't even ping it. Traced the cable to the switch, the light was out, moved the cable to a new port and everything was happy again.
Work on issues from the bottom up not the top down. I should have checked the cable first and made sure I could pinf the box before wondering if the NAS was down or locked up. |
|
| said by Aranarth_t:Work on issues from the bottom up not the top down. qft |
|
