Forgot to mention something... I am running Zone Alarm suite. When I unplugged Cat5, I also disabled ZA in case the firewall was blocking wireless data. No luck with that either.
Is my new PCI adapter DOA?
I have just finished building a new Media Center computer. I have it up and running fine on a wired DSL internet connection along with 2 other computers. No problems there. However, I want use this new computer in the living room without running a Cat5 line all through the house. (DSL modem/router is in home office) There I decided to install a wireless adapter in the new computer. I am running Windows 7 Premium Home Edition.
This is the hardware:
Internet service provider ATT DSL
Modem/Router: 2wire 2701 HG-B (Displaying 4 green status lights... No wireless light)
PCI adapter Card: Rosewill RNX-N300X http://www.newegg.com/Product/Product.aspx?Item=N82E16833166051
The Problem: Card does not detect any wireless networks at all.. (know there are at least 2 wireless networks running close by) There is a setup utility that came with card that when ran is supposed to show all kinds of pretty color charts about wireless networks. When I ran the utility, NO DATA at all was displayed.
What I have done so far to try to fix the problem:
(1) Downloaded and installed newest drivers from mfg. website
(2) Device Manager shows nothing wrong. No red "X"s; no yellow "?"
(3) Unpluged Cat5 cable and ran network diagnostic testing which indicated
that there was something wrong with the device driver.
(Why the conflict between Device Manager & network Diagnostic testing?)
(4) TCP/IP stack repair options for use with Vista or Windows 7.
Start, All Programs\Accessories and right click on Command Prompt, select
"Run as Administrator" to open a command prompt.
In the command prompt window that opens, type type the following
commands, each followed by the Enter key:
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Done all that
(5) I read in another thread that you might find this information useful, so here it is.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Darrell>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : MediaCenter
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 40-61-86-87-A1-1B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c52e:ef93:5dd8:fdc9%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, July 03, 2010 12:23:41 PM
Lease Expires . . . . . . . . . . : Sunday, July 04, 2010 12:23:40 PM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 239100294
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-B7-9F-95-40-61-86-87-A1-1B
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.gateway.2wire.net:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:34f4:34bc:9cbd:572d(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::34f4:34bc:9cbd:572d%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Thanks in advance for you time and effort. Hope we can get this card up and running... Really don't want to do a RMA on it.
This is the hardware:
Internet service provider ATT DSL
Modem/Router: 2wire 2701 HG-B (Displaying 4 green status lights... No wireless light)
PCI adapter Card: Rosewill RNX-N300X http://www.newegg.com/Product/Product.aspx?Item=N82E16833166051
The Problem: Card does not detect any wireless networks at all.. (know there are at least 2 wireless networks running close by) There is a setup utility that came with card that when ran is supposed to show all kinds of pretty color charts about wireless networks. When I ran the utility, NO DATA at all was displayed.
What I have done so far to try to fix the problem:
(1) Downloaded and installed newest drivers from mfg. website
(2) Device Manager shows nothing wrong. No red "X"s; no yellow "?"
(3) Unpluged Cat5 cable and ran network diagnostic testing which indicated
that there was something wrong with the device driver.
(Why the conflict between Device Manager & network Diagnostic testing?)
(4) TCP/IP stack repair options for use with Vista or Windows 7.
Start, All Programs\Accessories and right click on Command Prompt, select
"Run as Administrator" to open a command prompt.
In the command prompt window that opens, type type the following
commands, each followed by the Enter key:
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Done all that
(5) I read in another thread that you might find this information useful, so here it is.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Darrell>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : MediaCenter
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 40-61-86-87-A1-1B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c52e:ef93:5dd8:fdc9%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, July 03, 2010 12:23:41 PM
Lease Expires . . . . . . . . . . : Sunday, July 04, 2010 12:23:40 PM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 239100294
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-B7-9F-95-40-61-86-87-A1-1B
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.gateway.2wire.net:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:34f4:34bc:9cbd:572d(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::34f4:34bc:9cbd:572d%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Thanks in advance for you time and effort. Hope we can get this card up and running... Really don't want to do a RMA on it.
- Status
- Not open for further replies.
1 - 15 of 15 Posts
There is no evidence of a wireless adapter in that IPCONFIG.
Hold the Windows key and press R, then type devmgmt.msc
Please respond to all the following steps.
It would be best if you could post a screen shot of Device Manager with the Network adapters and Other devices sections expanded.
To post a screen shot of the active window, hold the Alt key and press the PrtScn key. Open the Windows PAINT application and Paste the screen shot. You can then use PAINT to trim to suit, and save it as a JPG format file. To upload it to the forum, open the full reply window and use the Manage Attachments button to upload it here.
Hold the Windows key and press R, then type devmgmt.msc
Please respond to all the following steps.
- Under Network adapters, please tell me all the devices listed.
- Are there any devices under Network adapters that have a red x displayed?
- Also, are there any devices anywhere in the Device Manager display with yellow ? or ! displayed?
It would be best if you could post a screen shot of Device Manager with the Network adapters and Other devices sections expanded.
To post a screen shot of the active window, hold the Alt key and press the PrtScn key. Open the Windows PAINT application and Paste the screen shot. You can then use PAINT to trim to suit, and save it as a JPG format file. To upload it to the forum, open the full reply window and use the Manage Attachments button to upload it here.
Check that all your network services are Started:
Note: You can check the services in Control Panel, Administrative Tools, Services.
All of these services should be started, and their startup type should be automatic (or perhaps manual).
If a service is not running, open it's properties and check the dependencies. Check each of the dependencies and see which one is preventing the service from running. Checking the event log is also a good idea here, there may be clues to what is failing.
- COM+ Event System (for WZC issues)
- Computer Browser
- DHCP Client
- DNS Client
- Network Connections
- Network Location Awareness
- Remote Procedure Call (RPC)
- Server
- TCP/IP Netbios helper
- Wireless Zero Configuration (XP wireless configurations only)
- WLAN AutoConfig (Vista wireless configurations only)
- Workstation
Note: You can check the services in Control Panel, Administrative Tools, Services.
All of these services should be started, and their startup type should be automatic (or perhaps manual).
If a service is not running, open it's properties and check the dependencies. Check each of the dependencies and see which one is preventing the service from running. Checking the event log is also a good idea here, there may be clues to what is failing.
All Listed services have started with no failures indicated. Most on automatic, 2 on manual. There are even a couple of services running that are listed by same name as adapter.
Hello,
I would take it out and reseat it again or move the card to a different PCI slot.
I would take it out and reseat it again or move the card to a different PCI slot.
I moved the adapter to another PCI Slot, but that didn't solve anything.. What is funny (odd) is that windows 7 knows the card is there and identifies it properly. Where was another odd thing that happened.. After I installed the card in the computer the first time, I updated the drivers for mfg. web site.. When I switched slots and booted the computer, windows re-installed drivers from it's files..
I also ran Belarc Advisor just for fun.. Guess what.. Belarc not only identified the card properly, but also listed IP address for the whole network including the adapter card. In other words, Belarc shows a complete network (including wireless) that should work.. Only problem, it doesn't work at all.
Which brings me back to the question I asked to start this thread. "Is the adapter DOA?" (defective out of the box)
Still looking for ideas.
I also ran Belarc Advisor just for fun.. Guess what.. Belarc not only identified the card properly, but also listed IP address for the whole network including the adapter card. In other words, Belarc shows a complete network (including wireless) that should work.. Only problem, it doesn't work at all.
Which brings me back to the question I asked to start this thread. "Is the adapter DOA?" (defective out of the box)
Still looking for ideas.
At this point, I'd suspect the NIC is dead, time to try another one.
Thanks for taking the time to try to help me.. I went back to the product reviews for this item at Newegg.. Reading deep in the reviews, I discovered there seems to be a problem of DOA units. People report that they either work great or not at all. Gonna call mfg. tomorrow ref. RMA. I guess I should appreciate my good fortune with Newegg. I have been dealing with them since the days of the AMD Socket 754 and this is my first RMA.
I've had a few RMA's with Newegg, but they've all gone pretty smoothly.
Your "N" Wi-Fi card may not be dead but the Zone Alarm Secuity Suite you have installed could be partially blocking the driver installation without your knowledge. I've encountered a similar problem recently with my computer, which runs on Windows 7 (64-bit). After the installation, everything appeared to be OK but I couldn't see any available networks. I spent the better part of a day trying to figure out what was wrong to no avail. I decided to give it a try on another computer, which also runs on Windows 7. The only difference is that it is a 32-bit version. I ended up with the same predictament. After those experiences, I decided to RMA the card back to the seller and get a refund.
I went back to the same seller and ordered another "N" Wi-Fi card from a different brand. When that one arrived, I installed it and the results were the same as the returned card. I was thinking that the chances of receiving two defective cards (in my case, both cards used the same chipset [RaLink RT2760T]) were very slim so the problems I was having must be caused by something else. I suspected that it's possible the security software (I use the freeware versions of Zone Alarm and Avast) may be the culprit. Turns out, I was right.
I first uninstalled the drivers for the Wi-Fi card then I went to the Device Manager to make sure the drivers were completely uninstalled. After that, I disabled Avast so that it wouldn't start with the next computer reboot and temporarily uninstalled Zone Alarm. I restarted the computer and the generic Wi-Fi driver automatically installed, enabling me to connect to my network once I inputted the encryption password. Once that was done, I reinstalled Zone Alarm and enabled Avast again.
If I were you, I would go to the Wi-Fi card manufacturer's website and download their latest drivers. Just install the drivers, leaving out the utility program if you are offered a choice.
Hope this helps you in some way. :smile:
I went back to the same seller and ordered another "N" Wi-Fi card from a different brand. When that one arrived, I installed it and the results were the same as the returned card. I was thinking that the chances of receiving two defective cards (in my case, both cards used the same chipset [RaLink RT2760T]) were very slim so the problems I was having must be caused by something else. I suspected that it's possible the security software (I use the freeware versions of Zone Alarm and Avast) may be the culprit. Turns out, I was right.
I first uninstalled the drivers for the Wi-Fi card then I went to the Device Manager to make sure the drivers were completely uninstalled. After that, I disabled Avast so that it wouldn't start with the next computer reboot and temporarily uninstalled Zone Alarm. I restarted the computer and the generic Wi-Fi driver automatically installed, enabling me to connect to my network once I inputted the encryption password. Once that was done, I reinstalled Zone Alarm and enabled Avast again.
If I were you, I would go to the Wi-Fi card manufacturer's website and download their latest drivers. Just install the drivers, leaving out the utility program if you are offered a choice.
Hope this helps you in some way. :smile:
peterdmar - this is an old Thread, perhaps OP already figured out and resolved his issue.
Thanks for the feedback, I'm sure than it will benefit others.
Thanks for the feedback, I'm sure than it will benefit others.
1 - 15 of 15 Posts
- Status
- Not open for further replies.
Tech Support Forum
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!
Full Forum Listing
Top Contributors this Month
View All
spunk.funk
139 Replies
SpywareDr
56 Replies
wolfen1086
43 Replies
Recommended Communities
