Author Topic: Windows 7 - file and printer sharing will not turn on and stay on (Read 40188 times)

rudolph963 · « **Reply #25 on:** November 07, 2015, 06:40:28 am »

Tried windows firewall repair, will try turning off AV and windows firewall again. Rapport EI64 is refering to IBM Trusteer Rapport provided by our bank as security. It hasn't ever caused any problems that I am aware of. Tried and still get the same result. Tried all the above and the Server and Computer Browser still giving error 1068, file and printer sharing still will not activate.

Boggin · « **Reply #26 on:** November 07, 2015, 08:59:24 am »

I'd love to see a pic of the Errors in Event Viewer as well as your registry, but as your Snipping Tool isn't working....

I've looked around for a solution to that and came across that Trusteer Rapport can disable the Snipping Tool.

Did that reinstate after you uninstalled it in Device Manager and is it still listed in Programs and Features to uninstall ?

rudolph963 · « **Reply #27 on:** November 07, 2015, 10:38:09 am »

Shutdown Trusteer and snipping started working.

Boggin · « **Reply #28 on:** November 07, 2015, 02:58:38 pm »

You are getting the PerfNet error because Server isn't started - so we're back to square on that one and the VSS error is normal according to MS.

https://technet.microsoft.com/en-us/library/dd364925(v=ws.10).aspx

I was hoping to find something else was stopping Server from starting, but still up against a brick wall until we can ID which other service it needs to be started when it isn't listed in any of the Dependencies.

I don't know if you can use File and Printer Sharing in Safe Mode with Networking, but can you check to see if it remains on in that mode ?

As an aside, after shutting down Rapport is the yellow alert still next to Teredo Tunneling in Device Manager ?

rudolph963 · « **Reply #29 on:** November 07, 2015, 04:13:59 pm »

The yellow alert is still next to the Microsoft Teredo Tunneling Adapter. I will try file and printer sharing in safe mode and see if it works. Thanks.
Doesn't do anything.

Julian · « **Reply #30 on:** November 08, 2015, 12:48:40 am »

hmmm okay so boggin went through a lot with you let's see have you ran tweaking repairs 2 times in safe mode (with networking) meaning open windows repair run the program after running all default repairs restart go back in safe mode(with networking) run the default repairs again? if so after that (in normal mode) open a cmd type in

Code: [Select]

wmic service list brief that will show us your services and say if its running or not. after you run that command take a screen shot of the services it pulls up (may take 2 screenshots) i wanna see which services are enabled/disabled as well as ok or not. but my main thinking is if BITS or BFE is messed up.

rudolph963 · « **Reply #31 on:** November 08, 2015, 07:34:08 am »

Yes, Tweaking repairs at least once in safe mode after running Tweaking firewall repair. Screenshots attached.

Boggin · « **Reply #32 on:** November 08, 2015, 08:00:33 am »

Is that all it gave you - what's happened to the As and Bs etc.

rudolph963 · « **Reply #33 on:** November 08, 2015, 08:09:09 am »

Don't know, but they aren't there. I had to run wmic service list brief from the command prompt. If you try to run otherwise it runs but the closes immediately.

Boggin · « **Reply #34 on:** November 08, 2015, 08:16:17 am »

Just go into services and check Background Intelligent Transfer Services and Base Filtering Engine.

The former is just showing as Manual and BFE is showing as Started and Auto in mine.

If there'd been any problems with BFE then I would have expected you to get an error message that Windows Firewall was stopped.

rudolph963 · « **Reply #35 on:** November 08, 2015, 08:20:09 am »

Both flagged as started

Boggin · « **Reply #36 on:** November 08, 2015, 08:35:12 am »

Well, they say no two Win 7 machines are the same

Just to confirm they are running, can you go Start - type msconfig and press enter, then check their status as running under the Services tab.

While you are in there, can you scroll a bit further down and check that the box for Server is checked.

rudolph963 · « **Reply #37 on:** November 08, 2015, 08:44:38 am »

They are running. Box next to Server is checked but the process is stopped

Boggin · « **Reply #38 on:** November 08, 2015, 08:55:14 am »

I've just been checking mine and my Lanman Server is showing as Started and Auto to yours which is showing as Stopped and Auto, although I've deleted the SMB 1 key, so don't know if that would have any effect.

There's no listing for it in services.msc so not sure if it would require a net start command.

Julian may have a comment on that.

There was one item I noticed that you have in the registry snip that I don't and that is for AutoShareWks with a value of 0.

I don't know what that is for or whether it's relevant.

An easy way to post the output of a cmd window is to right click in the text area and then click on Select all and press enter.

You then just right click in the reply box and select Paste, but the way you have done it may reduced its overall size.

EDIT - Forget about AutoShareWks - it's to do with enabling Administrative shares and the default value appears to be 0.

Boggin · « **Reply #39 on:** November 08, 2015, 09:54:38 am »

I can't think of anything else to suggest for this.

The idea of checking in Safe Mode with Networking was to eliminate the possibility of a 3rd party agent preventing Server from starting.

If anything else was failing to start, that would have been repetitive in Event Viewer as was PerNet and I doubt if scrolling further down the list of Errors in Event Viewer would show anything different.

While you are waiting for Julian to get back, see if these cmds will resolve the yellow alert next to Teredo Tunneling -

1. As an administrator from the Cmd Prompt, type then press Enter after each of these commands :-
2. netsh
3. int teredo
4. set state disabled
5. Open Device Manager/View/Show hidden devices > right click on Teredo Tunneling Pseudo-Interface and select Uninstall
6. Open the Cmd Prompt as an administrator again and type then Enter these cmds :-
7. netsh
8. int ipv6
9. set teredo client
10. Open Device Manager/Action/Scan for new hardware.
11. Then select Show hidden devices from the View menu.

It should now display without the yellow alert.

An alternative is to create a restore point then after uninstalling Teredo, click on Action/Add legacy hardware then click Next until you see the left pane populate and select Network adapters - Next - Microsoft then scroll down the right pane to see the Microsoft one - click on that and Next and when done, check to see that it is reinstated without any yellow alerts.

As I said earlier, it was HitmanPro.Alert v3.0 which is a browser guard which put a yellow alert next to mine, which is why I asked you to check if yours was still there after turning off Rapport.

rudolph963 · « **Reply #40 on:** November 08, 2015, 10:14:19 am »

I did the above and there is no yellow alert except for rapport ei64. There also is no listing for microsoft teredo tunneling adapter, so no yellow alert for it.

Julian · « **Reply #41 on:** November 08, 2015, 02:26:16 pm »

Quote from: rudolph963 on November 08, 2015, 07:34:08 am

Yes, Tweaking repairs at least once in safe mode after running Tweaking firewall repair.

did you just run repair number 6 repair Windows firewall? Try running all the default repairs. There is a button under the repairs above the system monitor click that button to select all the default repairs.

Boggin · « **Reply #42 on:** November 08, 2015, 03:15:03 pm »

Quote from: rudolph963 on November 08, 2015, 10:14:19 am

I did the above and there is no yellow alert except for rapport ei64. There also is no listing for microsoft teredo tunneling adapter, so no yellow alert for it.

Use the alternative method via Action/Add legacy hardware to reinstate it.

I've been looking up Lanman Server as yours is showing as stopped and that may be the key.

From this article http://computerstepbystep.com/server_service.html run a cmd prompt as an admininstrator and enter this cmd to see what it returns.

net start LanmanServer

shutdown /r /t 00 (to reboot if successful)

BTW - Who has locked this thread ?

rudolph963 · « **Reply #43 on:** November 08, 2015, 05:24:44 pm »

okay, I ran Tweaking in safe mode and did the two things you asked above and enclose screenshots.

Julian · « **Reply #44 on:** November 08, 2015, 09:03:05 pm »

Okay have you done a chkdsk at all or an sfc /scannow ??

Boggin · « **Reply #45 on:** November 09, 2015, 01:09:07 am »

sfc /scannow was to be my next suggestion after running a scan with the free version of MBAM.

https://www.malwarebytes.org/mwb-download/

Uncheck the box for the trial Premium version during install and before running the scan, click on Settings/Detection and Protection and use the dropdown if necessary to Treat PuPs and PuMs as Malware.

This program inserts itself into the Startup/Services menu of msconfig and can be set to Disabled in services.msc as well as being unchecked in msconfig.

Run the sfc /scannow after the MBAM scan but let us know if it finds any malware.

If the sfc /scannow reports that it is unable to repair some files, then enter the following cmd which will put an icon onto the Desktop.

This will open the CBS log in Notepad which you can then copy & paste into the reply box.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt

The forum may allow you to copy & paste the cmd to the cmd prompt to avoid typos, although it doesn't always for me.

rudolph963 · « **Reply #46 on:** November 09, 2015, 04:55:13 am »

Malwarebytes only found one thing, Dell System Detect, which I had previously told it to ignore.

rudolph963 · « **Reply #47 on:** November 09, 2015, 07:30:33 am »

Fixed - Downloaded Hotfix for srvnet.sys from Microsoft and it fixed the File and Printer Sharing. I have not checked the fax error mentioned in the sfc report.

https://support.microsoft.com/en-us/kb/2473205

Boggin · « **Reply #48 on:** November 09, 2015, 09:13:44 am »

When I was researching srvnet earlier I came across another Hotfix but it didn't apply to any errors you were getting and as you only apply a Hotfix for the published errors, ignored it - but glad you found the right Hotfix to sort it.

rudolph963 · « **Reply #49 on:** November 09, 2015, 10:58:57 am »

Guess I got lucky. Thanks for your help