Can browse LAN but not internet

M

markyb

Hello, a bizarre problem on a friends network with wireless router:
All OK till 3 days ago. Now Desktop PC (XP using built in firewall
only) can browse LAN OK but not access internet. No ping to internet IP
addresses. The PC has both wired and wireless network connections both
set to obtain DNS and IP automatically. Both working fine on LAN. No
Spyware or viruses detected by scan.
My friend also has a laptop with wireless card and this can connect to
the internet as usual.
I have checked all the router settings to see if that is blocking
access but all seems well and none have been changed since PC was able
to connect.
I have trawled the newsgroups for a possible solution and followed the
instructions in many of the network troubleshooters available without
success.
Has anyone come across a similar problem and if so were you able to
resolve it?
Thanks for any input!
Mark
 
C

Chuck

Hello, a bizarre problem on a friends network with wireless router:
All OK till 3 days ago. Now Desktop PC (XP using built in firewall
only) can browse LAN OK but not access internet. No ping to internet IP
addresses. The PC has both wired and wireless network connections both
set to obtain DNS and IP automatically. Both working fine on LAN. No
Spyware or viruses detected by scan.
My friend also has a laptop with wireless card and this can connect to
the internet as usual.
I have checked all the router settings to see if that is blocking
access but all seems well and none have been changed since PC was able
to connect.
I have trawled the newsgroups for a possible solution and followed the
instructions in many of the network troubleshooters available without
success.
Has anyone come across a similar problem and if so were you able to
resolve it?
Thanks for any input!
Mark
Click to expand...

Mark,

By "ping to internet IP addresses", does this mean, specifically, that you are
pinging Internet hosts, by IP address, that ARE accessible from the laptop? And
both the desktop and laptop are connected to the same LAN?

If so, let's look at IP configuration. Please post "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-internet-service.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-internet-service.html#AskingForHelp

If my assumptions stated in the first paragraph are correct, you may benefit
from looking at the MTU setting:
<http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html>
http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html
 
M

markyb

Thanks for the quick reply!
Your assumtion in first paragraph is correct!
I'll check out those links and post back tomorrow with ipconfig.
Regards,
 
M

markyb

Hi ran all the checks I could find on your excellent site!

First results from my own laptop which I took to my friends house
tonight. (Laptop connected to internet with no problems)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Admin>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network
Connecti
on
Physical Address. . . . . . . . . : 00-08-02-DB-00-F0

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Toshiba Wireless LAN Mini
PCI Card
Physical Address. . . . . . . . . : 00-02-2D-57-19-49
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : 28 March 2006 20:05:04
Lease Expires . . . . . . . . . . : 11 February 1905 13:36:48

C:\Documents and Settings\Admin>ping www.yahoo.com

Pinging www.yahoo.akadns.net [68.142.226.46] with 32 bytes of data:

Reply from 68.142.226.46: bytes=32 time=276ms TTL=55
Reply from 68.142.226.46: bytes=32 time=104ms TTL=56
Reply from 68.142.226.46: bytes=32 time=116ms TTL=56
Reply from 68.142.226.46: bytes=32 time=112ms TTL=55

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

C:\Documents and Settings\Admin>ping 66.94.230.33

Pinging 66.94.230.33 with 32 bytes of data:

Reply from 66.94.230.33: bytes=32 time=187ms TTL=56
Reply from 66.94.230.33: bytes=32 time=190ms TTL=56
Reply from 66.94.230.33: bytes=32 time=189ms TTL=56
Reply from 66.94.230.33: bytes=32 time=184ms TTL=56

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

C:\Documents and Settings\Admin>tracert 66.94.230.33

Tracing route to p2.www.scd.yahoo.com [66.94.230.33]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.2.1
2 25 ms 13 ms 13 ms lo99.sfd-1-dsl.as9105.net
[212.74.111.241]
3 29 ms 25 ms 15 ms ge1-2-26.sfd1.as9105.net
[212.74.106.190]
4 130 ms 22 ms 14 ms pos0-0.not0.as9105.net [212.74.108.205]
5 33 ms 29 ms 27 ms ge1-1.not1.as9105.net [212.74.108.213]
6 30 ms 27 ms 29 ms pos0-0.lei1.as9105.net [212.74.109.225]
7 39 ms 25 ms 31 ms ge1-1.lei0.as9105.net [212.74.109.221]
8 39 ms 29 ms 27 ms pos2-0.sa-bham0.as9105.net
[212.74.109.214]
9 43 ms 42 ms 42 ms pos6-0.mk1.as9105.net [212.74.108.13]
10 42 ms 40 ms 28 ms pos4-0.mk0.as9105.net [212.74.111.198]
11 37 ms 43 ms 40 ms pos3-0.lon10.as9105.net [212.74.108.10]
12 * 39 ms 27 ms ge-4-0-0.lon11.ip.tiscali.net
[213.200.77.73]
13 109 ms 104 ms 110 ms so-1-0-0.was10.ip.tiscali.net
[213.200.81.89]
14 112 ms 115 ms 110 ms 213.200.66.126
15 184 ms 182 ms 188 ms so-3-1-0.pat1.pao.yahoo.com
[216.115.101.128]
16 182 ms 181 ms 189 ms ge-4-0-0-p440.msr1.scd.yahoo.com
[216.115.106.20
1]
17 185 ms 185 ms 183 ms ten-2-3-bas1.scd.yahoo.com
[66.218.82.221]
18 185 ms 181 ms 190 ms p2.www.scd.yahoo.com [66.94.230.33]

Trace complete.

C:\Documents and Settings\Admin>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time=2ms TTL=128
Reply from 192.168.2.1: bytes=32 time=2ms TTL=128
Reply from 192.168.2.1: bytes=32 time=3ms TTL=128
Reply from 192.168.2.1: bytes=32 time=2ms TTL=128

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

C:\Documents and Settings\Admin>ping 192.168.2.3

Pinging 192.168.2.3 with 32 bytes of data:

Reply from 192.168.2.3: bytes=32 time=2ms TTL=128
Reply from 192.168.2.3: bytes=32 time=2ms TTL=128
Reply from 192.168.2.3: bytes=32 time=2ms TTL=128
Reply from 192.168.2.3: bytes=32 time=2ms TTL=128

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

C:\Documents and Settings\Admin>ping -f -l 1500 192.168.2.1

Pinging 192.168.2.1 with 1500 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Admin>ping -f -l 1495 192.168.2.1

Pinging 192.168.2.1 with 1495 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Admin>ping -f -l 1492 192.168.2.1

Pinging 192.168.2.1 with 1492 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Admin>ping -f -l 1491 192.168.2.1

Pinging 192.168.2.1 with 1491 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Admin>


Now results from Desktop (No internet connection)


First the desktop:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\KHE>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth PAN Network
Adapter
Physical Address. . . . . . . . . : 00-11-09-54-18-71
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.2.10
Lease Obtained. . . . . . . . . . : 28 March 2006 09:47:45
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA VT6105 Rhine III Fast
Ethernet A
dapter
Physical Address. . . . . . . . . : 00-11-09-A3-99-E3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : 28 March 2006 09:47:24
Lease Expires . . . . . . . . . . : 11 February 1905 03:19:08

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : RT2500 USB Wireless LAN
Card
Physical Address. . . . . . . . . : 00-11-09-4D-FD-8B

C:\Documents and Settings\KHE>ping www.yahoo.com
Ping request could not find host www.yahoo.com. Please check the name
and try ag
ain.

C:\Documents and Settings\KHE>ping 66.94.230.33

Pinging 66.94.230.33 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.94.230.33:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\KHE>tracert www.yahoo.com
Unable to resolve target system name www.yahoo.com.

C:\Documents and Settings\KHE>tracert 66.94.230.33

Tracing route to 66.94.230.33 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Documents and Settings\KHE>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

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

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

C:\Documents and Settings\KHE>ping 192.168.2.12

Pinging 192.168.2.12 with 32 bytes of data:

Reply from 192.168.2.12: bytes=32 time=98ms TTL=128
Reply from 192.168.2.12: bytes=32 time=2ms TTL=128
Reply from 192.168.2.12: bytes=32 time=2ms TTL=128
Reply from 192.168.2.12: bytes=32 time=2ms TTL=128

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

C:\Documents and Settings\KHE>ping 192.168.2.12 -f -l 1472

Pinging 192.168.2.12 with 1472 bytes of data:

Reply from 192.168.2.12: bytes=1472 time=39ms TTL=128
Reply from 192.168.2.12: bytes=1472 time=13ms TTL=128
Reply from 192.168.2.12: bytes=1472 time=13ms TTL=128
Reply from 192.168.2.12: bytes=1472 time=13ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1500 192.168.2.1

Pinging 192.168.2.1 with 1500 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\KHE>ping -f -l 1420 192.168.2.1

Pinging 192.168.2.1 with 1420 bytes of data:

Reply from 192.168.2.1: bytes=1420 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1420 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1420 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1420 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1430 192.168.2.1

Pinging 192.168.2.1 with 1430 bytes of data:

Reply from 192.168.2.1: bytes=1430 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1430 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1430 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1430 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1440 192.168.2.1

Pinging 192.168.2.1 with 1440 bytes of data:

Reply from 192.168.2.1: bytes=1440 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1440 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1440 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1440 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1450 192.168.2.1

Pinging 192.168.2.1 with 1450 bytes of data:

Reply from 192.168.2.1: bytes=1450 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1450 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1450 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1450 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1460 192.168.2.1

Pinging 192.168.2.1 with 1460 bytes of data:

Reply from 192.168.2.1: bytes=1460 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1460 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1460 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1460 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1470 192.168.2.1

Pinging 192.168.2.1 with 1470 bytes of data:

Reply from 192.168.2.1: bytes=1470 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1470 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1470 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1470 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1480 192.168.2.1

Pinging 192.168.2.1 with 1480 bytes of data:

Reply from 192.168.2.1: bytes=1480 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1480 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1480 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1480 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1490 192.168.2.1

Pinging 192.168.2.1 with 1490 bytes of data:

Reply from 192.168.2.1: bytes=1490 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1490 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1490 time<1ms TTL=128
Reply from 192.168.2.1: bytes=1490 time<1ms TTL=128

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

C:\Documents and Settings\KHE>ping -f -l 1495 192.168.2.1

Pinging 192.168.2.1 with 1495 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\KHE>

Now the result of running Browstat on Friend's laptop (Connects to
internet OK)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\KHE>browstat status


Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{4DF5A9AC-FA26-42F0
-8B97-0BB5DC2BE7CE}
Browsing is active on domain.
Master browser name is: HOME
Master browser is running build 2600
1 backup servers retrieved from master HOME
\\HOME
There are 1 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{4D
F5A9AC-FA26-42F0-8B97-0BB5DC2BE7CE}
There are 3 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{4D
F5A9AC-FA26-42F0-8B97-0BB5DC2BE7CE}

C:\Documents and Settings\KHE>

Hope this helps with the troubleshooting. I checked registry on both
laptops and desktop and no values for MTU are present.

Thanks again for your help!

Regards,
Mark
 
C

Chuck

Hi ran all the checks I could find on your excellent site!

First results from my own laptop which I took to my friends house
tonight. (Laptop connected to internet with no problems)
Click to expand...

Hope this helps with the troubleshooting. I checked registry on both
laptops and desktop and no values for MTU are present.

Thanks again for your help!

Regards,
Mark
Click to expand...

Hi Mark,

If this isn't the only problem, it certainly won't help things:

Windows IP Configuration

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

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth PAN Network Adapter
Physical Address. . . . . . . . . : 00-11-09-54-18-71
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.1 <== (1)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.2.10
Lease Obtained. . . . . . . . . . : 28 March 2006 09:47:45
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA VT6105 Rhine III Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-11-09-A3-99-E3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1 <== (1)
DHCP Server . . . . . . . . . . . : 192.168.2.1 <== (1)
DNS Servers . . . . . . . . . . . : 192.168.2.1 <== (1)
Lease Obtained. . . . . . . . . . : 28 March 2006 09:47:24
Lease Expires . . . . . . . . . . : 11 February 1905 03:19:08

What did you change 3 days ago? Maybe run the Network Setup Wizard? Look at
(1) above. The primary Ethernet adapter on Britannia uses a Default Gateway,
DHCP Server, and DNS Server of 192.168.2.1. Look at the secondary Ethernet
adapter (aka Bluetooth PAN Network Adapter). It has an IP address of
192.168.2.1, and a DHCP server of 192.168.2.10.

So what is this 192.168.2.10? There's your problem. It is assigning an address
which conflicts with the router.
 
M

markyb

Hi, Chuck
Yes spotted that last night but as it is a bluetooth connection that is
never used didn't think it relevant.
I'll disable the bluetooth adapter and if that sorts the problem
re-enable and correct the settings.
Thanks for taking the time to help. I'll post back with the results!
Regards,
Mark
 
M

markyb

Yep - That was it!
Turns out he'd connected his new phone and installed activesync and
associated bluetooth software that day. Forgot to mention that to me
though!
Many thanks once more for taking the time to help me out.
Cheers,
Mark
 
C

Chuck

Yep - That was it!
Turns out he'd connected his new phone and installed activesync and
associated bluetooth software that day. Forgot to mention that to me
though!
Many thanks once more for taking the time to help me out.
Cheers,
Mark
Click to expand...

Kewl. Don't you love easily diagnosed problems? Glad it worked out.

Cheers,

Chuck
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Working LAN, but no client Internet -Again 14
Wins XP Desktop PC - wired network cannot access Internet or MSN L 1
Wired and wireless file sharing between XP and Leopard (PC and MAC 7
LAN & Internet Setup Problem with DI-524 2
Can Windows Firewall affect LAN traffic ? 7
Internet Browse Issue 2
Wireless home network share problem 10
Can Telnet to router but not browse 1

Top