[chris kirk]

I'm on cable, and we're using a DLink DI-614+ router, a DWL-1000AP+ Access point for my roommate, and a DWL-520+ RevisionE wireless card for me. The router is in the guest house, and i'm in the front of the main house, so i get an extremely weak signal which likes to drop out on me from time to time. Because of this, i'm trying to install a repeater, a DWL-800AP+... At first, when i had the thing rigged up, i couldn't even get it connected.. but i stopped and disabled the WZC service and, via the task manager, killed dlink's proprietary ANIWZCS process. Now I can connect to the repeater, but i only stay connected for about 10 seconds, when i stop being able to send/recieve. If I use the repair function, i can get connected again for another 10 seconds. i've been tearing my hair out over this one for the past couple nights, but i can't seem to figure it out, after hours browsing forums and knowledge bases. DLink's tech support has been pretty useless as well. they just sent me a form letter telling me how to log into the web based configuration (argh!)... anyone have any other ideas???

=--c.k-->

[Advertisements]

Nobody has any sort of input on this?? :(

c'mon guys i'm tearing my hair out over here... any help at all would be appreciated.

=--c.k-->

[chris kirk]

Nobody has any sort of input on this?? :(

c'mon guys i'm tearing my hair out over here... any help at all would be appreciated.

=--c.k-->

[Dan]

Hi Chris,

I'm sorry, but I'm in the same boat as you on this one... It would help alot if you could give me some assurance that it is actually a hardware issue; can you by any chance get some one elses PC/laptop over to your place, to attempt a connection?

There are some tests we could run to see what's happening... But if it is a hardware issue, there's not much I can do to help. So, feel free to try the following:

Goto Start, Run, type CMD, press 'OK' and then type: IPCONFIG /ALL - please post the results here by right-clicking on the Command Prompt window, selecting 'Select All', pressing Ctrl+C, and then posting on this forum.

Test your Network
1. Goto Start, Run, type: NETSH DIAG GUI - press 'OK'. A Command Prompt window will open temporarily; don't touch it, it will disappear in a moment.
2. A Microsoft Help and Support window will then open; select the option 'Scan your system'.
3. Wait for the scan to finish and then scroll down to the heading 'Modems and Network Adapters'. Look at 'Network Adapters' (don't expand it yet). Beside your connection information, you should see a green 'PASSED'; if you do not (if you see a red 'FAILED') then expand 'Network Adapters', scroll down the list until you see the heading with the 'FAILED', expand that option and copy and paste the results here.
In the NETSH DIAG GUI, you should be looking for any red 'FAILED', however the key one is Network Adapters for you. If you see any other red FAILED, expand the component and copy the results.

Goto Start, Run, type CMD and press 'OK' - now type: PATHPING YAHOO.COM - please copy and paste the results by right-clicking on the Command Prompt window, selecting 'Select All', and then pressing Ctrl+C. Please post the results here.

Please goto Start, Run, type CMD and press 'OK' - now type: netstat -rn and press enter; please post the results here.

Let me know how you go.. Sorry I can't be of more help.
Dan.

[chris kirk]

well i don't think it's hardware because my roommates computer, which is running win2000, does just fine with the repeater...

the situation has changed just a little bit though, i have NO connection whatsoever from my comp. tried disabling the firewall, enabling WZC, using WZC or the in-house utility provided by DLink... nothing.. only thing that works is to take my roommates AP/Client and plug it into my NIC.. the results below are from that connection..

The next post will be the information from the other, non-working, connection.

-----------------------------------------------------------------------------------------

Microsoft Windows XP [Version 5.1.2600]

Windows IP Configuration

Host Name . . . . . . . . . . . . : box
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.ca.comcast.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.ca.comcast.net
Description . . . . . . . . . . . : Intel® PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-11-11-E6-6B-B3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Wednesday, January 11, 2006 3:49:01 PM
Lease Expires . . . . . . . . . . : Wednesday, January 18, 2006 3:49:01 PM

-----------------------------------------------------------------------------------------

DefaultIPGateway = 192.168.0.1(Same Subnet) (FAILED)
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=4ms TTL=4
Request timed out.
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss)
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 4ms, Average = 4ms

DHCPServer = 192.168.0.1 (FAILED)
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=5ms TTL=5
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=4ms TTL=4
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms

-----------------------------------------------------------------------------------------

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:23981 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1026 0.0.0.0:0 LISTENING
TCP 127.0.0.1:10110 0.0.0.0:0 LISTENING
TCP 192.168.0.101:139 0.0.0.0:0 LISTENING
TCP 192.168.0.101:1070 38.116.139.254:80 ESTABLISHED
TCP 192.168.0.101:1171 38.115.131.131:2240 ESTABLISHED
TCP 192.168.0.101:1198 200.185.240.153:2234 ESTABLISHED
TCP 192.168.0.101:1211 82.120.205.182:2234 ESTABLISHED
TCP 192.168.0.101:1213 201.215.197.115:4511 ESTABLISHED
TCP 192.168.0.101:1218 85.206.153.91:32671 ESTABLISHED
TCP 192.168.0.101:1226 216.86.178.65:16014 SYN_SENT
TCP 192.168.0.101:1227 200.126.166.85:7229 ESTABLISHED
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1025 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1027 *:*
UDP 127.0.0.1:1031 *:*
UDP 127.0.0.1:1033 *:*
UDP 127.0.0.1:1043 *:*
UDP 127.0.0.1:1181 *:*
UDP 192.168.0.101:123 *:*
UDP 192.168.0.101:137 *:*
UDP 192.168.0.101:138 *:*

-----------------------------------------------------------------------------------------


Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>pathping yahoo.com
Unable to resolve target system name yahoo.com.

C:\Documents and Settings\Owner>pathping yahoo.com

Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:
0 box.hsd1.ca.comcast.net [192.168.0.101]
1 192.168.0.1
2 10.235.48.1
3 24.130.2.145
4 24.130.8.18
5 12.127.137.21
6 gbr5-p90.la2ca.ip.att.net [12.123.28.193]
7 tbr1-p013501.la2ca.ip.att.net [12.122.11.137]
8 tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
9 tbr2-cl13.attga.ip.att.net [12.122.2.90]
10 tbr1-cl1835.attga.ip.att.net [12.122.9.157]
11 12.122.10.69
12 gar1-p390.ascva.ip.att.net [12.123.8.53]
13 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 box.hsd1.ca.comcast.net [192.168.0.101]
27/ 100 = 27% |
1 4ms 31/ 100 = 31% 4/ 100 = 4% 192.168.0.1
0/ 100 = 0% |
2 11ms 31/ 100 = 31% 4/ 100 = 4% 10.235.48.1
0/ 100 = 0% |
3 11ms 27/ 100 = 27% 0/ 100 = 0% 24.130.2.145
2/ 100 = 2% |
4 11ms 34/ 100 = 34% 5/ 100 = 5% 24.130.8.18
0/ 100 = 0% |
5 13ms 29/ 100 = 29% 0/ 100 = 0% 12.127.137.21
71/ 100 = 71% |
6 --- 100/ 100 =100% 0/ 100 = 0% gbr5-p90.la2ca.ip.att.net [12.123.28.193]
0/ 100 = 0% |
7 --- 100/ 100 =100% 0/ 100 = 0% tbr1-p013501.la2ca.ip.att.net [12.122.11.137]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% tbr2-cl13.attga.ip.att.net [12.122.2.90]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% tbr1-cl1835.attga.ip.att.net [12.122.9.157]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% 12.122.10.69
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar1-p390.ascva.ip.att.net [12.123.8.53]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% box [0.0.0.0]

Trace complete.
----------------------------------------------------------------------------------------------------------


=--c.k--->

[chris kirk]

and from the other (my wireless nic) connection....


-------------------------------------------------------------------------------------------------------

Windows IP Configuration

Host Name . . . . . . . . . . . . : box
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : D-Link Air DWL-520 Wireless PCI Adap
ter(rev.E)
Physical Address. . . . . . . . . : 00-0D-88-58-99-00



Nothing failed in NETSH DIAG GUI -- couldn't make any outward connections (happens about 1/2 the time), and pathping was unable to resolve yahoo.com...

[Dan]

Chris,
You're right; this does not look like a Hardware issue.

only thing that works is to take my roommates AP/Client and plug it into my NIC

Could you please expand on this?

So you're still attempting to connect your computer through his AP/Client?

Could you please verify that your computer is free of Malware by following the steps located here.

Thanks,
Dan.

[chris kirk]

what i was doing before is just connecting directly to the router.. that stopped working all of a sudden and now i have to take my roommates wireless client (DWL-1000ap+) and plug it straight into my nic to get a connection to the router.

i don't know if that's all the information you need...

anyway, i'm off to run through the malware paces.. let me know what you think.

[Dan]

Chris,

This is sounding more like a Malware issue to me than a Hardware issue; it appears to be getting progressively worse, whereas a hardware issue would generally remain constant unless the hardware is dying.

So, please continue with the Malware steps and let me know if you find anything.

NOTE: I would recommend running many of the programs in Safe Mode.