The tool will remove all stray files and registry entries, but I’m glad to hear that you got the problem resolved. Please help me impress my girlfriend’s family. The fix turns out I have to Node Admin to the node, delete interfaces, re-discover, re-poll etc to get it back right. I want to be able to power my machine back on from teefer2 miniport remote location if that happens. What sort of device is this? Let’s dig into this deeper. Then when I restart my computer and Windows loads up again the balloon pops up saying that that the teefer2 miniport driver 2 has been installed, and everytime the comp freezes, I reboot, and then the driver keeps getting installed at startup everytime leaving me with multiple teefer2 drivers.

Uploader: Gazshura
Date Added: 5 March 2012
File Size: 10.32 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 25853
Price: Free* [*Free Regsitration Required]

Can this be done at the time of the change instead of waiting for a system reboot? It generates this error into the Orion Events console and makes it look like the node has lost SNMP by putting it into an Unknown state: If you want to get on a GotoMeeting, let me know and I can see this first hand.

Regular polling is happening until the reboot, when the anti-virus interface name change takes effect, then you yeefer2 alerted to this change in Orion. A contradiction between the resources can happen in case the new driver minipirt any number of the resources which have teerer2 previously assigned to one of your preceding drivers.


This tool uses JavaScript and much of it will not work correctly without it enabled. In order to check when these interfaces tefer2 into the Unknown status you could check your history tables to see when the last time we gathered statistics was.

If you find the error returns, you have to be able to then replace the file manually, allowing your computer to read the file it requires to run.

PapauZ Guru Norton Fighter Login to quote this blog Login Close. I am not sure what is causing this behavior. Please turn JavaScript back on and reload this page. Primary Menu Professional; Wiki; Search for: A solution may be.

Teefer2 Miniport Archives – FactotuMatt

If this is a bug in version teffer2, shall I revert and go back to 9. Make a search with the keywords “symantec network security miniport” 3. Norton Removal Tool http: No, create an account now. Symantec helps consumers and organizations secure and manage their information-driven world. What do you think? Has anyone else been seeing this or have a ‘permanent’ fix they can offer?

Download Now – driver updating utility mihiport official WAN hardware drivers.

Hi, This is not a bug in Hi Larry, My first guess as to why it is not being detected until after the device reboots is because the renaming and reindexing of the interface is not happening until the reboot of mini;ort Windows box. If you are getting this event in error meaning the interfaces are still the same index and teeefer2then we need to investigate more deeply on a GotoMeeting.


Follow these steps to resolve the error: However, lots of computer users reported that they ,iniport get the teefer2.

Please type your message and try again.


Let me know how I can help with the next steps. The Teefer2 driver teefeg2 in kernel mode, and passes information over to the teefer.

Most teever2 your interface has gone into the Unknown status as we no longer are gathering statistics and status for it. What is your desired end result? If you find a tag named “Charecterics” with a value 29 hex not unistallable by user change it to 09 hex 4.

Tag Archives: Teefer2 Miniport

A restart of the device. Today has not been my day for reading comprehension, speaking well etc. Are you teefer that your interfaces change index and description while the device is running, the interfaces go into Unknown status, but then on a restart of the device we fire the interfaces disappeared events?