Internet Connection

[Rostum]

Is there anyway I can have my internet connection load up and try to connect after all my processes / programs have all loaded when booting up my computer?

Because, for some odd reason, when even I boot up my computer, it'll load the internet connection before everything else, and will say it is connected. But it won't be able to actually connect to the internet. But when I disable it and then enable it (without changing any settings at all), it works fine.

[rubah]

What kind of connection is it?

[Rostum]

Just a normal LAN connection (it's wireless, but it happens the same with ethernet).

[o_O]

Is is a DSL/cable connection or dialup? Or pseudo-dialup?

It should automatically start up and work if it's a DSL or cable connection. can you post the results of these commands performed <i>before</i> you fix the connection:

Click Start > Run, and run "cmd". To copy/paste from cmd, you can click the top menu > mark, and then press enter after it is marked.

Commands:
1. "ipconfig /all"
2. "tracert google.com"
3. "ping google.com"
4. "ping 72.14.207.99"
5. From command #1, there will be one section called "Wireless network connection" (or "Local area connection" if you're using ethernet), or something similar; look for the default gateway and the IP address of the relevant section (they'll be similar to 192.168.*.*, 10.*.*.* or 175.*.*.*), and try "ping <gateway/ip>" replacing the <gateway/ip> with the default gateway address and then again with the IP address.

[Rostum]

It's just a normal 1.5Mbps ADSL connection.

1.

Windows IP Configuration

Host Name . . . . . . . . . . . . : logandowell
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-09-6B-AF-AE-A9

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR WG111v2 54Mbps Wireless USB
2.0 Adapter
Physical Address. . . . . . . . . : 00-18-4D-02-A7-32
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
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. . . . . . . . . . : Monday, 19 March 2007 8:51:18 AM
Lease Expires . . . . . . . . . . : Tuesday, 20 March 2007 8:51:18 AM

2.


Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms www.routerlogin.com [192.168.0.1]
2 17 ms 17 ms 16 ms lns3-loopback-0.Melbourne.netspace.net.au [203.1
7.101.67]
3 143 ms 244 ms 243 ms core1-cr-gigether-5-2-11.Melbourne.netspace.net.
au [203.10.110.195]
4 135 ms 18 ms 21 ms 408.ge-1-1-0.GW3.MEL1.ALTER.NET [203.166.93.197]

5 17 ms 16 ms 18 ms 423.AT-6-0-1.XR2.MEL1.ALTER.NET [210.80.33.157]

6 29 ms 29 ms 29 ms so-0-1-0.XT2.SYD4.ALTER.NET [210.80.33.9]
7 190 ms 190 ms 190 ms 0.so-4-1-0.IR2.LAX12.Alter.Net [210.80.48.97]
8 191 ms 193 ms 192 ms 0.so-5-0-0.IL2.LAX9.ALTER.NET [152.63.48.69]
9 191 ms 191 ms 191 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
10 187 ms 188 ms 187 ms 0.so-7-0-0.BR1.LAX7.ALTER.NET [152.63.112.153]
11 194 ms 192 ms 193 ms so-6-0-0.mpr2.lax9.us.above.net [64.125.13.77]
12 232 ms 232 ms 230 ms so-4-1-0.mpr1.iah1.us.above.net [64.125.29.106]

13 230 ms 229 ms 229 ms so0-0-0.mpr4.iah1.us.above.net [64.125.26.14]
14 249 ms 249 ms 248 ms so-4-0-0.mpr1.atl6.us.above.net [64.125.29.69]
15 244 ms 242 ms 243 ms 64.124.229.173.google.com [64.124.229.173]
16 246 ms 247 ms 253 ms 72.14.236.12
17 263 ms 250 ms 250 ms 72.14.236.173
18 262 ms 268 ms 267 ms 216.239.49.222
19 263 ms 263 ms 264 ms 216.239.49.226
20 261 ms 261 ms 263 ms 64.233.187.99

Trace complete.

3.

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=264ms TTL=239
Reply from 72.14.207.99: bytes=32 time=263ms TTL=239
Reply from 72.14.207.99: bytes=32 time=263ms TTL=239
Reply from 72.14.207.99: bytes=32 time=263ms TTL=239

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 263ms, Maximum = 264ms, Average = 263ms

4.

Pinging 72.14.207.99 with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=263ms TTL=239
Reply from 72.14.207.99: bytes=32 time=264ms TTL=239
Reply from 72.14.207.99: bytes=32 time=264ms TTL=239
Reply from 72.14.207.99: bytes=32 time=262ms TTL=239

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 262ms, Maximum = 264ms, Average = 263ms

5.
Ping IP Address

Pinging 192.168.0.2 with 32 bytes of data:

Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping Default Gateway

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
Reply from 192.168.0.1: bytes=32 time=2ms TTL=255

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

[o_O]

The only strange thing I can see there is that before you restart the connection the wifi adapter is using the DNS server 192.168.0.1.
That will definitely cause problems if the DNS servers for your ISP aren't stored in your router.
It is possible that on boot, your computer is just leasing 192.168.0.1 for the DNS servers, but releasing and renewing the DHCP lease obtains the correct addresses.

What type of router have you got? Also, can you post the output of "ipconfig /all" after you refresh the connection?

What's your ISP?

[Rostum]

My ISP is Netspace, and I'm using a new Netgear (http://www.netgear.com/Products/RoutersandGateways/GWirelessRouters/WGR614.aspx) modem/router. I also have an iMac connecting to it wirelessly, as well as a Dell Laptop.

They seem to run fine on it.

And, just to mention, this has only happened in the last couple of weeks. I've been using this for a year and nothing like this has ever happened.

[o_O]

It's possible that you need to statically assign DNS servers.

If the problem machine is a Windows XP one, click Start > run and run ncpa.cpl.
Right click wireless network connection and select properties. Double click Internet Protocol (TCP/IP) and change the bottom dot to use the following DNS servers.

In the boxes, put the following information:
Primary: 203.10.110.101
Secondary: 203.17.103.1

Note: These DNS servers are what Google turned up. The Netspace website doesn't seem to have any info on their servers, so I recommend you give them a call just to find out the correct numbers.
Upon searching a bit more, this info also popped up for Netspace DNS servers:
Primary: 210.15.254.240
Secondary: 210.15.254.241

It's not uncommon for ISPs to frequently change their DNS server addresses, so one of those is probably older (but both are still likely to work). It doesn't really matter which ISP's DNS servers you use; you could put some european ones in there if you really wanted, but using your own ISP's is theoretically faster because of geographic distance.

[Rostum]

Hmm, I used Netspace's DNS addresses, and it still connects. But I still have to disable and re-enable it.

Maybe this might have something to do with it. The way I do it is this:

- Connection starts with Windows Configuration enabled (can't connect).
- Disable Windows Configuration.
- Enable Windows Configuration again (can connect).