-
So.. my motherboard has a pair of Marvell Yukon 88E8056 adapters on it and Running Windows 7 Ultimate 64bit, URLSnooper fails to detect any of the adapters..
its a ASUS P6T Deluxe V2, X58, Socket-1366 motherboard with a CoreI7 920 cpu and 12GB of ram..
any ideas? I tried URL Hunter in trial/demo mode and it at least did catch urls so it seems like WinPCap isnt the issue..
and all this because im after the MMS to http://wmlive.bbc.co.uk/wms/england/lrlondon =)
-
this is so bizzarre that url snooper isn't finding adapters but you are saying other winpcap sniffers are.. i'm just at a loss as to why that might be.. anyone have any clues?
-
me too.. I dont get it either.. I tried URL Hunter specifically because .. apart from its ugly ass looks.. it seems to be quite similar AND relies on WinPCap as well..
in URLSnooper the adapter selection box just has a red frame around it.. buhuuing that theres no adapters.. I tried both of the connectors on the PC but doesnt seem to make a difference.. tried one disabled one enabled.. etc..
Also the WinpCap doesnt show up as a protocol loaded in the Local Area Connection Properties for Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller .. but I'm guessing thats a Windows 7 thing that it doesnt show up there?
Maybe its not getting properly installed and URL Hunter is _faking it_ ? I noticed I was unable to find the MMS protocol in the URL Hunter window but I thought that could be cos it was in trial/demo mode?
Anything else I should try perhaps?
-
.. well I just installed and tested Wireshark.. it says WinPCap IS installed.. and also works so.. it has to be a URL Snooper issue.. whatever it may be...
-
Ok i'm going to have another look.. i wish i could reproduce the problem.. i wonder if it could have something to do with running as administrator.. if you run the other program as administrator, do they still see the network adapters?
-
both url hunter and wireshark works when run as administrator..just tested..
during the OMG IT DOESNT WORK/DESPERATION TESTING OF ANYTHING-mode I was having yesterday I even tried running the installers for both urlsnooper and winpcap separately as admin and that made no difference either..
-
i appreciate all the help testing this -- there is no reason url snooper shouldnt work -- it may simply be a case of me needing to update the network adapter detection code i use to account for some winpcap change.. i'll try to get it done this week. if you don't mind i'll email you and maybe you can help me test some test versions in the next day or two?
-
sure, email away! :)
-
Got the same problem on my XP SP3.My onboard network adapter is Marvell 88E8039.
Here's a snapshot http://img410.imageshack.us/img410/830/urls.png.
-
mm RENI, what is that adapter for dialup thing?.. I dont even get that.. mine is totally blank
-
Reni, when you test the adapter in the pic, does it come up as a Success or a Failure to Detect? On my other PC (the one that works and shows 3 adapters), a generic dial-up adapter is one of the working adapters (from memory of using it a couple days ago.)
I wonder if there's a way of sourcing every available adapter on our PC and linking them up with URL Snooper. That would give us alot more adapters to test.
-
All adapters should be detected automatically; im going to work on this on sunday and see if i can spot anything strange with my winpcap interface.
-
Ok so can i ask anyone who is having trouble with urlsnooper not reporting all or any adapters to download windump from the winpcap site:
http://www.winpcap.org/windump/install/bin/windump_3_9_5/WinDump.exe
Then open up a commandline prompt where the windump.exe executable is, and run: windump -D
(note that the D must be capitalized)
And let me know if windump reports a different list of adapters than url snooper does.
-
sent you a PM with the results.. obviously as it DID discover them and URL Snooper didnt.. the results _are_ different ..
hope it helps you figure this out..
-
ok that's a good sign.. getting closer then.
-
ixxo says the new version fixes the problem, so let's see if everyone else agrees. try downloading version 2.26.01 from the web page (https://www.donationcoder.com/Software/Mouser/urlsnooper/index.html) (or using updater).
-
mm RENI, what is that adapter for dialup thing?.. I dont even get that.. mine is totally blank
-ixxo
Well,I don't know what the hell is that either. :P
Reni, when you test the adapter in the pic, does it come up as a Success or a Failure to Detect? On my other PC (the one that works and shows 3 adapters), a generic dial-up adapter is one of the working adapters (from memory of using it a couple days ago.)
I wonder if there's a way of sourcing every available adapter on our PC and linking them up with URL Snooper. That would give us alot more adapters to test.
-jamessnooper
Unfortunately,It's a Failure. :'(Ok so can i ask anyone who is having trouble with urlsnooper not reporting all or any adapters to download windump from the winpcap site:
http://www.winpcap.org/windump/install/bin/windump_3_9_5/WinDump.exe
Then open up a commandline prompt where the windump.exe executable is, and run: windump -D
(note that the D must be capitalized)
And let me know if windump reports a different list of adapters than url snooper does.
-mouser
Here's my result:
C:\***>windump -D
1.\Device\NPF_GenericDialupAdapter (Adapter for generic dialup and VPN capture)
C:\***>
-
ixxo says the new version fixes the problem, so let's see if everyone else agrees. try downloading version 2.26.01 from the web page (https://www.donationcoder.com/Software/Mouser/urlsnooper/index.html) (or using updater).
-mouser
Still not working... :o
http://i46.tinypic.com/kalhte.jpg
-
well automatic detection/selection still fails for me but.. now at least the adapters shows up in the list so I can choose myself and THEN it works
maybe your adapter RENI is one that the WinpCap library doesnt support? I know theres a few it doesnt, but I dont know wich ones..
what about trying some other apps and see if they work?.. If for example wireshark works then its a urlsnooper specific problem.. if it too fails or only shows the same VPN thing then you may have to look at WinpCap itself..
-
As ixxo says, forget about automatic network adapter detection -- as it says on its window when it cant find an adapter, there are many reasons why this may fail and it's not important. the issue is really whether your network adapter is available in the options.
And the key to see if this is a url snooper program or a winpcap problem is to run that windump test.
RENI, you pasted your results from windump, which says that winpcap/windump can only see one generic dialup adapter -- and that seems to be what urlsnooper on your computer can see.. so there's really nothing more urlsnooper can do i'm afraid, as it is doing all that winpcap can do.
Assuming that this adapter is not the one you actually use, then the situation is as ixxo says, and it may be that you are using an adapter that winpcap is not able to work with. Best thing in such case is to go to the winpcap support page (http://www.winpcap.org/contact.htm) and see if you can find any solution.
-
failed to find a suitable net driver , I selected the adapter mannually.
G:\TDDOWNLOAD\1>windump -d
windump: listening on \Device\NPF_{07A20FC8-6C36-4EEE-8172-EB7BF3EE9F9B}
(000) ret #96
Failed to initialize network adapter WinPcap Network adapter 'Marvell Yukon Ethernet Controller.' on local host.
-
How adjust detection of adapter menually
-
Choose from the File Menu -> "Advanced Mode"
then select your adapter on the "General Options" tab.
-
As ixxo says, forget about automatic network adapter detection -- as it says on its window when it cant find an adapter, there are many reasons why this may fail and it's not important. the issue is really whether your network adapter is available in the options.
And the key to see if this is a url snooper program or a winpcap problem is to run that windump test.
RENI, you pasted your results from windump, which says that winpcap/windump can only see one generic dialup adapter -- and that seems to be what urlsnooper on your computer can see.. so there's really nothing more urlsnooper can do i'm afraid, as it is doing all that winpcap can do.
Assuming that this adapter is not the one you actually use, then the situation is as ixxo says, and it may be that you are using an adapter that winpcap is not able to work with. Best thing in such case is to go to the winpcap support page (http://www.winpcap.org/contact.htm) and see if you can find any solution.
-mouser
OK,yesterday I switched to Windows 7 x86 with 11.10.5.3 marvell driver installed.Suddenly the Marvell 88E8039 appears in the adapter list and snooper is working smoothly. :P
-
hi, i'm using win7 and havig the same problem.
i installed the latest ver 2.26.01.
on wireshark there are the same adapters, and the sniffing works just fine, but the ursnooper doesn't work, even on manual mode when i select the same adapter.
any ideas?
-
hi eliramd,
when you say urlsnooper doesn't work -- can you be more specific?
are you saying that you see the adapter, and when you click to sniff and browse the web, you can see the packet count increasing in the url snooper status bar, but that it's just not returning results you expect?
-
thanks for returning so quickly.
i choose the adapter manualy, but the packets are not counted.
(it is the right adapter since the wireshark has the same list, in the same order, and over there i can see the packets count)
i don't see anything in the captured even when it is set to 'show all'
-
if you click the "Sniff Network" button, and then open up your web browser and start sniffing around, do you see the bottom status bar start showing a count of how many packets received?
-
no, all it is saying that it's sniffing using winpcap, the adapter name & the IPs of the computer
-
what this suggests to me is that maybe you haven't selected the right adapter.. are you sure it's the one you are actually using? and are you saying that wireshark does get information from using this same adapter?
the only other thing i can think of is that maybe you have the "only scan this computer" checkbox unchecked, and that the adapter is refusing to operate in promiscuous mode?
-
on another thread: https://www.donationcoder.com/forum/index.php?topic=21343.msg196952#msg196952
it was suggested to try UNCHECKING the "only scan this computer" checkbox -- try that too.
-
I speculate that installing WireShark somehow breaks UrlSnooper. UrlSnooper worked for me until I installed WireShark. Now, even after uninstalling WireShark, UrlSnooper cannot autodetect the adapter. Maybe you should look into it by installing WireShark on your own system? The list of adapters shows up fine, but none of them return any results when sniffing packets.
-
that is troubling.. does the problem persist after a computer restart?
-
I have a similar problem, I guess - after installing Windows 7, adapters are found ("Network adaptor 'Microsoft' on local host" (x2, for some reason), and "Network adaptor 'Marvell Yukon Ethernet Controller.' on local host"), but they don't work. I'm currently running on a wireless (Intel WiFi 5300), and if I recall correctly, this was the only one which worked under Vista, which is... missing now, haha. Windump only lists these 3, as well. I've uninstalled URL Snooper, Winpcap, reinstalled, run as admin, but nada.
Any help would be greatly appreciated!
-
i tried running it after restart, and without that chack box, but no metter what test i make i get no results from the URL Snooper.
on my system beside the wireshark a VirtualPC is installed.
i'm about to format & reinstall my computer (the win7 RCis expired). i'll install the new computer with the URLSnooper & without the wireshark, & i'll let you know what the results are.
-
More about what I suspect: WireShark does something to prevent UrlSnooper to work.
Not sure if I alters WinPcap (as I believe I reinstalled it at one point) or some other file.
mouse, do you know if there are any other files/programs that UrlSnooper depends on - such as some DLLs or something - that WireShark may be altering?
-
that is very strange.. i can't think of how it would or why it would happen, but i'd love to get some confirmation. i can try it on a virtual machine too.
-
hi,
formated & reinstalled the computer without the wireshark, and the URLSnooper is working.
i didn't install all of the program i had on the old computer, but it's looking like that the wireshark is as guilty as hell.
hope i won't need it in the neer future :)
-
that is really intriguing.. so same hardware, same operating system?
-
Win7 64bit ultimate and URL Snooper v2.26.01 here
URL Snooper doesn't detect my Atheros AR928X wireless card.. it shows the same list as
D:\>WinDump -D
1.\Device\NPF_{1DE7B2FF-BDA0-49C6-BD19-73582F3B0866} (Microsoft)
2.\Device\NPF_{2D645593-CA05-418B-833E-DFEC05BF020B} (Realtek RTL8168C(P)/8111C(P) Family PCI-E GBE NIC)
3.\Device\NPF_{F85F9D11-D155-447F-8954-727EBB6BAB80} (Microsoft)
=\
-
hi, im not using a laptop and my internet connection is using the usb based wireless internet connector (3G Modem), in short, it does not uses my nic to connect to the internet. On the network drop down adapter menu i have SIS adapter and microsoft network adapter. so will this program work on this kind of internet setup? thanks for the reply
-
this is a followup on my post, I hope someone would help me. thanks
-
hi lacnel0t, sorry for delay in replying.
i'm afraid i don't have any experience running the software on your kind of setup.
the best i can suggest is that you try the winpcap support forums and see if anyone knows anything about getting the winpcap driver to work with that modem.
http://www.winpcap.org/contact.htm
-
I'm having a similar problem. I'm on Win7 x64 using Winpcap 4.1.2 and URLSnooper2 2.28.01. It won't autodetect my adapter and it's not in the list. I'm using a wireless adapter (onboard - Intel) and in URLSnooper it has listed Microsoft, Microsoft, TAP-Win32 Adapter V9, and Broadcom Netlink Gigabit Ethernet driver. Autodetect fails every time. When I run windump -d I get the following output:
windump: listening on \Device\NPF_{0C2B00A0-B520-4434-AFE1-6AD19B283BAE} (000) ret #96
I tried each of the listed adapters manually and sniffed around but it came back with nothing each time.
I tried running URLSnooper as an admin and in compatibility mode for Vista and XP SP2 with no change. I'm wondering about the auto detect adapter string, which by default says "Privacy". Where is this line of text supposed to be coming from? Google's index page or where exactly?
Is there anything else I could try to manually add my adapter such as the registry keys for URLSnooper or any adjustments for the settings?
Thanks in advance,
pogue
-
I'm wondering about the auto detect adapter string, which by default says "Privacy". Where is this line of text supposed to be coming from? Google's index page or where exactly?
yes -- it's simply looking to see a specific string in the page it retrieves, in this case the string "Privacy" expected on the google page. when found it means the page was seen.
first advice: completely forget about automatic network adapter detection -- just turn it off, it serves no value except to save you the trouble of selecting your adapter from the drop down list.
the real problem is your intel wireless adapter may not be supported by winpcap.
-
I'm wondering about the auto detect adapter string, which by default says "Privacy". Where is this line of text supposed to be coming from? Google's index page or where exactly?
yes -- it's simply looking to see a specific string in the page it retrieves, in this case the string "Privacy" expected on the google page. when found it means the page was seen.
first advice: completely forget about automatic network adapter detection -- just turn it off, it serves no value except to save you the trouble of selecting your adapter from the drop down list.
the real problem is your intel wireless adapter may not be supported by winpcap.
-mouser
Well, I played around with it a bit more and logged into a VPN I use that uses OpenVPN and low and behold URLSnooper was able to sniff traffic through the TAP-Win32 Adapter V9 driver.
Strange that Winpcap wouldn't support my wireless driver, as it's the standard Intel onboard adapter that comes with many laptops. It's the Intel Wifi Link 1000 BGN. Here's a screen shot of my device drivers screen with the 2 Microsoft adapters, Intel wifi, ethernet, and TAP-Win32 drivers listed. URLSnooper just doesn't see the Intel one.
http://img695.imageshack.us/img695/6199/networkadapters.jpg
I did upgrade from Winpcap 3.1.1 to 3.1.2 prior to making this post, but I haven't tried updating the wifi adapter's drivers from the vendor/Intel. Does Winpcap publish a list of adapters they support? Any other suggestions?
Thanks for the help mouser.
-
there are definitely winpcap problems with some wireless adapters -- i think especially intel. it's unfortunate but i don't know much more.. the winpcap site used to have an archived discussion list somewhere but it's hard to find now and im not sure where it is.
-
there are definitely winpcap problems with some wireless adapters -- i think especially intel. it's unfortunate but i don't know much more.. the winpcap site used to have an archived discussion list somewhere but it's hard to find now and im not sure where it is.
-mouser
I think I found it
http://www.winpcap.org/misc/faq.htm#Q-16
Windows NT4/2000/XP/2003/Vista/2008/Win7/2008R2: the packet driver works ok on Ethernet networks. As for dial-up adapters and VPN connections, read Q5 and Q6. As in Win9x, FDDI, ARCNET, ATM and Token Ring are supported, but not tested by us.
Wireless adapters: these adapters may present problems, because they are not properly supported by the Windows Kernel. Some of them are not detected, other don't support promiscuous mode. In the best case, WinPcap is able to see an Ethernet emulation and not the real transiting packets: this means that the 802.11 frames are transformed into fake Ethernet frames before being captured, and that control frames are not received.
-
This is an old thread, but here's hoping.
URL Snooper works fine until VPN is started, when it cannot detect the network adapter. Stop the VPN, and URL Snooper works fine. From an earlier post, there seems to be an issue with Winpcap and VPN.
Does anyone know of alternatives to Winpcap that do work with VPN?
Thanks.
-
mouser thank you . your Souloution Worked for me
-
Replay Media Catcher does a better job in detecting the network card by simply DISABLING/ENABLING it and intercepting the result.
Perhaps by implementing this strategy, UrlSnooper will see my card too:
1.\Device\NPF_{AF0A77D7-3B7F-4993-8D9D-F6D8F6827E04} (Intel(R) 82566DC-2 Gigabit Network Connection (Microsoft's Packet Scheduler) )
-
This may help some people. I use a VPN for connecting to the Internet. When I use URL Snooper with the VPN connected it fails to find my adapter. When I switch the VPN off and traffic is routed normally (rather than via a third party IP address) the Network Adapter is found by URL Snooper no problem at all. It's clear that (in my case at least) the use of a VPN (or possibly a proxy server) is creating problems with adapter detection.
I hope this helps some of you or at least shows you where to look.
-
...you can see the packet count increasing in the url snooper status bar, but that it's just not returning results you expect?
-mouser
Yes, I see packets get received in status bar, but the Net adapter certification still fails at the end.
Got XP/SP3 and nVidia's nForce networking controller onboard.
Any help would be appreciated.
-
If http://www.winpcap.org/windump/ is able to capture traffic, URL Snooper should too.
I'd suggest the following troubleshooting steps:
a) If opening google.com does not show the page in English at your location, choose google.com/en as URL (see https://www.donationcoder.com/forum/index.php?topic=25777.new#new)
b) check the packet.dll version shown with "WinDump.exe -?"
c) show the list of interfaces with "WinDump.exe -D", here is my output as example (the "Sun" NIC in my case does not see any web traffic):
1.\Device\NPF_{0C872E2B-E755-4BF5-B3FD-98E5E4BE8109} (Sun)
2.\Device\NPF_{85EE7CDF-2F35-492E-8382-1C805EAF4C32} (Intel(R) 82578DM Gigabit N
etwork Connection)
d) check if any network traffic is seen while surfing the web, when running "WinDump.exe -i 2" (replace "2" with the best matching NIC number from the previous step)
e) contact http://www.winpcap.org/contact.htm in case of problems with the information from b-d, but be aware of know problems with wireless adapters: http://www.winpcap.org/misc/faq.htm#Q-16
-
I'm running Windows 7 with Qualcomm Atheros WiFi adapter and Microsoft Virtual WiFi Miniport Adapter. When I run URL Snooper the only adapter detected is Network Adapter Microsoft on local host. Did anyone find a fix for this? - thanks
-
tkirklen, can you try doing what the post above made by Furty says to do?
-
All of these posts on this topic are very old but I still didn't see a fix for the issue after reading through them. So I'll try to see if someone can help me on the issue of my network adapters not being detected (anymore)
I'm having a problem getting winpcap to recognize my network adapters. WinPcap has worked for several years for me both on XP and Win7 OS. However just last week URLsnooper stopped detecting the network adapters. I've removed and installed both URLsnooper and WinPcap several times. I've troubleshot this as much as I can; not sure what else to do at this point. My devices have not changed; the only change made to my system is a Mozilla Firefox update. After noticing the issue with URLsnooper and WinPcap after this update I removed Mozilla and reinstalled the previous version. Still no luck. Thanks in advance for ANY help.
Operating System: Windows 7 Home Edition
My devices are:
Microsoft Virtual WiFi Miniport Adapter
Qualcomm Atheros AR9285 802.11b/g/n WiFi Adapter
Output from WinDump -D command:
1.\Device\NPF_{0C09BD3A-12E4-4366-AB44-5F4EC7F4E196} (Microsoft)
2.\Device\NPF_{AD3A071F-BAF4-44C1-9809-914873CB810F} (Microsoft)
Output from URLsnooper Network adapter dropdown
Network adapter 'Microsoft' on local host
Network adapter 'Microsoft' on local host
-
the URL Snooper doesn't show any URLs (option Show All) but
"WinDump.exe -D" recognizes 4 interfaces at my laptop, and with the last one (4.\Device\NPF_{C862B90B-4477-4755-8199-E18F11ED2D9D} (Microsoft) I can check network traffic.
what to do?
Windows 8 OS
-
can anyone help me?
-
hi migawka, sorry for the delay in replying.
if windump works, so should url snooper.
Does UrlSnooper show the same network adapters list as WinDump? Have you tried maybe running UrlSnooper as administrator?
-
yes, URLSnooper shows the same network adapters. I ran URLS as administrator - no change
-
I just noticed you are using Windows 8, migawka, and i see that winpcap has a new release with fixes for win8.
Have you tried installing the latest WinPCap, v4.1.3 (http://www.winpcap.org/install/default.htm) ?
I'm not sure if I need to build a new version in order to fix whatever problem you are having, but I will try to release a new version of UrlSnooper with the new winpcap release.
-
yes, I've instaled WinPCap v4.1.3
OS Windows 8, 64-bit