Chuck,
This is the ipconfig /all from the other computer. The connection to the
router was pretty weak.
Windows IP Configuration
Host Name . . . . . . . . . . . . : dads
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 VE Network
Connection
Physical Address. . . . . . . . . : 00-E0-B8-40-DB-94
Ethernet adapter Wireless Network Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys Wireless-G USB Network
Adapter with SpeedBooster v2
Physical Address. . . . . . . . . : 00-18-F8-32-63-37
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
IP Address. . . . . . . . . . . . : fe80::218:f8ff:fe32:6337%9
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 255.255.255.255
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
We have quite a bit of work ahead of us. I need for you to first read my
IPConfig article.
<
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html
That article shows you what a normal IPV4 configuration should look like. IPV4
is the Internet Protocol that has been used since IP was developed, 20 or so
years ago.
With Windows XP, Microsoft added IPV6, which is more complex and offers much
more addressing possibilities. Using IPV6, unfortunately, requires a network
running IPV6, and other computers doing so. So computers running IPV6 have to
run several flavours of IPV6 - Teredo Tunneling is the most common - so they can
work over an IPV4 network.
<
http://www.microsoft.com/technet/community/columns/cableguy/cg0506.mspx>
http://www.microsoft.com/technet/community/columns/cableguy/cg0506.mspx
<
http://www.microsoft.com/technet/prodtechnol/winxppro/evaluate/ipv6_teredo.mspx>
http://www.microsoft.com/technet/prodtechnol/winxppro/evaluate/ipv6_teredo.mspx
So the computer that works - "Dads" - appears to be only setup for IPV6 and
Teredo Tunneling. The problem computer - "Keiths" (yours?) - appears to be
setup for IPV4 and Teredo Tunneling.
Your IPV4 is whack too.
Your computer, and the subnet created by the router, appears to be on
10.10.1/24. Yet your DNS server is 192.168.1.254. Now, 192.168.1/24 is a
private subnet, so the only way that this should work would be if your WAN
connects into that subnet.
Yet you say that you were setup by a BellSouth tech, which implies that you have
BellSouth DSL? Who setup Dads?
Are these - Dads and Keiths - truly the only computers in your house (this is a
house, right?)??