However, nothing has changed apart from reformatting, so thusly I surmise it must be some kind of hidden file thing. Computers are so dang finicky. But as the enlightened internet user knows, a Google search can only take you so far. Truly, humanity is far superior to the machine in understanding what humans want to know. Machines are, luckily, inanimate objects which are subject to the input from humans, and thus not subject to arbitrary whim which has not been programmed into them. The typical Google search, as we should know by now, only yields page after page of results which are spam, outdated and specific results from no sooner than two to three years ago, and plagiarized information that fails to delve into substantial content. Here are the points which Google brings up, following counterpoints to why these are not the solution in this case:
* Position your router/adapter well. (Also: Reduce interference)
- The position of the router has not been changed since the computer was reformatted, and worked perfectly before.
* Replace the wireless antenna.
- The wireless antenna has not been changed, and worked perfectly before.
* Replace the wireless adapter.
- The wireless adapter has not been changed, and worked perfectly before.
* Add a wireless repeater.
- A wireless repeater was not required before to achieve a maximum signal.
* Change your wireless channel.
- The optimum wireless channel is already selected.
* Update your firmware/drivers/etc.
- The firmware/drivers being used come from the official websites for the hardware/software I am using, and are up to date.
* Disable Wireless Zero Configuration in Computer Management > Services.
- Before this had absolutely no effect. Just yesterday Windows Update released an update to the wireless router devices. After this update, disabling the Wireless Zero Configuration instead causes the computer to be unable to connect to the wireless network at all.
And so forth. And now, the merchandise: I was and still am using a Compaq Presario CR1750NX Desktop with an Amberine M motherboard running Windows XP Home SP2 with AT&T as ISP on a wireless network with a Netgear WPN111 wireless USB adapter allowing Windows to configure my wireless network settings.
Windows IP Configuration
Host Name . . . . . . . . . . . . : hal
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net
Ethernet adapter Wireless Network Connection 2:
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : NETGEAR RangeMax™ Wireless USB 2.0 Adapter WPN111
Physical Address. . . . . . . . . : 00-14-6C-E4-A3-AF
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.71
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Saturday, May 02, 2009 6:37:25 PM
Lease Expires . . . . . . . . . . : Sunday, May 03, 2009 6:37:25 PM
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=114ms TTL=241
Reply from 209.85.171.100: bytes=32 time=115ms TTL=241
Reply from 209.85.171.100: bytes=32 time=115ms TTL=241
Reply from 209.85.171.100: bytes=32 time=120ms TTL=241
Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 120ms, Average = 116ms
Pinging 209.85.0.171 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.85.0.171:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Tracing route to google.com [209.85.171.100]
over a maximum of 30 hops:
1 2 ms 2 ms 6 ms home [192.168.1.254]
2 23 ms 22 ms 23 ms 76-221-140-3.lightspeed.wlfrct.sbcglobal.net [76.221.140.3]
3 23 ms 23 ms 22 ms 75.12.207.134
4 24 ms 26 ms 50 ms 75.12.192.12
5 * 27 ms 37 ms 75.12.192.4
6 24 ms 22 ms 21 ms bb2-g5-0.wlfrct.sbcglobal.net [151.164.92.88]
7 27 ms 28 ms 27 ms 70.245.63.207
8 28 ms 30 ms 29 ms asn15169-google.eqnwnj.sbcglobal.net [151.164.248.202]
9 31 ms 32 ms 39 ms 72.14.238.232
10 60 ms 58 ms 53 ms 216.239.46.14
11 118 ms 188 ms 137 ms 72.14.233.116
12 114 ms * 116 ms 216.239.46.204
13 165 ms 149 ms 113 ms 216.239.48.141
14 116 ms 132 ms 115 ms 209.85.251.133
15 120 ms 128 ms 124 ms 74.125.31.130
16 119 ms 125 ms 114 ms cg-in-f100.google.com [209.85.171.100]
Trace complete.
Sign In
Create Account
