DonationCoder.com Software > UrlSnooper

Network Adapter Heavy Troublshooting plz

<< < (2/2)

4wd:
Since two of the network adapters are identified as nVidia MCP chipsets - are the users by any chance running the nVidia Network Manager?

This could be causing conflicts, (I know it was an absolute PITA when I had an nForce 3 chipset), and I'd never install it again.

I do still have an MCP78 chipset based PC, (XP Pro), so I'll install it on that for a test mouser but I'm not going to install flamin' NNM - dedication only goes so far :)

Supersnake:

Thanks for coming to my aid.

Since two of the network adapters are identified as nVidia MCP chipsets - are the users by any chance running the nVidia Network Manager?
Am really not sure how to check who is using it.  One moment and let me see if there is a running service....
OK, I launched services.msc and found NVIDIA Driver Helper Service running.  However, that is the service that the NVIDIA video drivers use. Will stop it anyway then relaunch URLSniffer and see if that helps..
Will get right back to you...

4wd:
The NNM, (can also be called the nVidia Network Access Manager), is usually an optional install included with the chipset drivers.

It allows things like Interface Teaming and did include firewall capabilities, I don't know if it does now - as I said, I avoid it like the plague.

BTW, you can permanently disable the NVIDIA Driver Helper Service, if nothing else it will decrease shutdown time.

Supersnake:
Hmm, I did disable the NVIDIA Driver Helper Service and of course the problem remained since it has nothing to do with the inability to access my nVidia Network Access Manager. Funny thing is I was trialing URLSnooper 6 weeks ago and it worked fine, however I have never had a need to use it again until tonight, so I thought I would give it another try.  If it worked then it should work tonight - thats strange.

Anyway, I just now installed another media packet sniffer called URL-Sniffer and it too has a nice GUI - but not as nice as URLSnooper.
However it generated  An attempt was made to access a socket in a way forbidden by its access permissions. so that didnt work.

I also tried another one whose name escapes me and it too had a nice GUI.  It detected both of my two network manager controllers/adaptors and even gave me the choice of having the program use either one.  However, no matter which of the two it chose it wasnt seeing any packets (was unable to).

Doesn't seem to make sense if URLSnooper worked 6 weeks ago and Windump is working tonight - that I cant get URLSnooper to work.

Am not going to mess around and disable or uninstall anything related to my chipset just for a non essential program  :)

Oh well, will play around with it some more.
Thank You

Supersnake:
Wait a minute. Let me read again what you wrote.

The NNM, (can also be called the nVidia Network Access Manager), is usually an optional install included with the chipset drivers.
-4wd (November 24, 2010, 10:30 PM)
--- End quote ---

Aha! Good to know that, thanks.  Since your telling me that, I learned that NVIDIA integrates ethernet drivers within its nVIDIA chip set driver too.

Have located a web discussion explaining reasons why Nvidia nForce Networking Controller #2 can appear; one of the reasons is when one adds a network router - which I did when I purchased and installed a D-link router to establish a wireless connection from my desktop computer to my laptop.  However, starting last week I no longer had a need to use my laptop at home - so I removed the router.  Apparently, I should have also uninstalled that 'controller #2' device driver.

So, I disabled the Nvidia nForce Networking Controller #2 in my Windows control panel and URLSnooper is working just fine now. Thanks for giving me the idea to suspect a driver conflict  :Thmbsup:


P.S. Will now make my donation too, thanks.
 

Navigation

[0] Message Index

[*] Previous page