When the Internet Security firewall is engaged, Intel(R) WiDi application running on my Windows 7 laptop cannot make a connection with the Netgear PTV2000 wireless TV adapter. A "could not obtain network address" error message is displayed on the TV to which the Netgear is connected. If I disable the AVG firewall and activate the Windows firewall, then everything works fine.
Has anyone else had any experience with the Intel WiDi program that would be helpful?
When I noticed that WiDiApp.exe runs a second program, PanDhcpDns.exe, tech support asked me to make sure both programs are in the Applications list, which I did, specifying "Allow All" for both. This too made no difference.
I have had an extended email conversation with tech support, but none of their suggestions have made any difference. I'm hoping that some users will have encountered either mine or a similar problem and have some light they can shed on it.
Diagnostic file wfmetcalf387.7z uploaded using ClickNFix...
Dear TechBuddy Ambassador:
Thank for your helpful and specific reply. I followed the "Troubleshooting...." article as completely as I could, and since the problem persisted, I ran avgfwdiag, and followed the instructions for that, and uploaded the results.
I also ran msinfo32 and have attached the compressed results in the file msinfo.7z to this post.
WiDiApp is unable to connect with my Netgear PTV2000..
Somewhere I read that I was supposed to start a new thread with as many details as possible.
The problem I've I having all along is that when I start Intel's WiDi application (v. 22.214.171.124), the Netgear PTV2000 (connected to my TV) reports on a TV screen error message that it is unable to access the network. The PTV2000 has IP 192.168.16.3 and my laptop is part of a small home network and has IP 192.168.0.20 . It is connected to a printer, my wife's computer, and my iPhone (WiFi) on the same network. The gateway of the LAN is a SMC8014WG has IP 192.168.0.1 . (The profile Test Netgear is a duplicate of Small Home or Office Network, with a few changes as instructed by AVG.)
This issue is 100% repeatable and predictable.
I'm fairly certain that Firewall is at fault here, because if I temporarily disable it and enable the Windows Firewall, the Netgear PTV2000 connects with my laptop without a hitch. No error or warning messages are displayed.
The purpose of the PTV2000 is convert my rather old TV into a semi-smart TV so that whatever is displayed on my laptop screen automatically appears on the TV.
Sometimes when the problem occurs, the network connection failure causes Windows 7 to report a message that WiDiApp has "stopped working". I displayed the detailed error message, saved it into a text file, and have attached it to this message.
Thanks for all your help.
P.S. At the moment I cannot access the version of the Netgear device software. I'll try to do so later on today, and if I'm successful, I'll post it in a separate message on this thread.
I hate to say this, but I added the Netgear address IP (192.168.16.3) to the IP addresses whitelist as you suggested, and it made no difference whatsoever.
Finally, in frustration, I added the ranges 192.168.0.1-192.168.0.255 and 192.168.16.1-192.168.16.255 first to the IP addresses whitelist and then to the list of Safe Networks. Neither of these made any difference either.
Seemingly the firewall is not blocking the IP address.
Personally, I think that either Firewall is blocking a third program associated with the Wireless Display (unlikely it seems to me) or it is treating the Netgear as an unknown access point and blocking it using the Mac address, as suggested in the article at http://www.avg.com/ww-en/faq.num-4676 because the Mac address does not match. If this is indeed the case, I have absolutely no idea how to fix it. :-(
Diagnostic files wfmetcalf325.7z and wfmetcalf871.7z uploaded using ClickNFix...
Thank you very much for getting back to me. :smile:
I followed your instructions carefully, and since the two AVGfwdiag.....zip files were much bigger than 2 MB, I used ClickNFix to send them to you. The name of the diagnostic package is wfmetcalf325.7z.
I used the utility specified in your link to gather all the AVG logs. Once again, because of length, I used another run of ClickNFix to send the file to you. The name of that diagnostic package is wfmetcalf871.7z.
I hope this information helps you out.
Once again, thanks so much for your patience and assistance.