Re: Host of networking problems ...

I did as you said by disabling ipv4 and restarted both computers to boot and
a few things changed. One, most notably and not sure how signifigant was the
disappearing of the gateway that I described as being disabled. I noticed
tho before it disappeared that it was also enabled and I'm not sure why.
Yesterday I ran the network wizzard a few times trying to get it to work
proper and I had some progress by maybe activating ICS like Tony said I
needed to but I'm not sure yet if I did, anyways I was thinking that was why
the gateway was enaled after I took off IPv6, but why did it disappear? I am
thinking it's a good thing because I know it wasn't needed to connect to the
internet and was just there as far as I know.

I did notice tho that the tunneling adapters are still there and not sure why.

Here is the latest config so far for pc 1.


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

C:\Documents and Settings\Reed>ping 192.168.3.2

Pinging 192.168.3.2 with 32 bytes of data:

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

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

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

Windows IP Configuration

Host Name . . . . . . . . . . . . : user-a15a222baf
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : no-domain-set.bellcanada

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-13-D4-A1-38-20
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : no-domain-set.bellcanada
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010
PCI
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-13-D4-A1-43-10
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
192.168.2.1
Lease Obtained. . . . . . . . . . : February 6, 2006 12:06:38 PM
Lease Expires . . . . . . . . . . : February 9, 2006 12:06:38 PM

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::5445:5245:444f%4
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : no-domain-set.bellcanada
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-02-0A
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.10%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-03-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.3.1%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Reed>


And here is the config data for pc 2:


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

C:\Documents and Settings\Owner>ping 192.168.3.1

Pinging 192.168.3.1 with 32 bytes of data:

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

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

C:\Documents and Settings\Owner>ping 192.168.2.10

Pinging 192.168.2.10 with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

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

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

Windows IP Configuration

Host Name . . . . . . . . . . . . : ATHELON1600XP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Eth
ernet NIC
Physical Address. . . . . . . . . : 00-50-FC-32-BB-F8
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

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::5445:5245:444f%4
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-03-02
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.3.2%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Owner>

So that's what it's saying so far. I'm going to try to figure out what Tony
sugested now and see how that fairs :-).

Thanks again for the patience and explaining these things to me.

"Chuck" wrote:

On Mon, 6 Feb 2006 08:05:31 -0800, Chrejo <Chrejo@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

"Chuck" wrote:

On Sun, 5 Feb 2006 14:35:35 -0800, Chrejo <Chrejo@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

(sigh) Where do I start ...

I have been working several hours now on my network problem and have gotten
nowhere. I have searched the newsletters and found good info but nothing for
my problem exactly.

It seems I can't figure out how to get my two computers to see eachother on
the network through a game, this is how it started. It also seems that I
can't get my other computer to even share the internet with this one (main
comp).
Ok, so I'll mention now that I'm using DSL and the ISP gives me a dynamic ip
that the modem comverts to a static one I see through DHCP as 192.168.2.10
(looks like a standard router ip). I'll also mention now that I have 2
network adapters (but acually three show up in network connections, the third
is listed as 1394 Net Adapter and is disabled) and I have a gateway that I'm
not sure why it's there but it's diabled (I think it installed with the ISP
software but unsure). There is only two ports at the back of my computer for
ethernet (but three adapters?) and those two adapters are the ones I'm trying
to use for the network. I basically have my Marvell Yukon 88E8001/8003/8010
PCI Gigabit Ethernet Controller as the one that conects to the internet
(modem) and my NVIDIA nForce Networking Controller as the one connected to my
second pc via crossover cable (both controllers are onboard). The second pc
has a Realtek RTL8139/810x Family Fast Ethernet NIC. I have no router.

I hope this isn't too much but i'll continue (sigh).
Ok, on to the software ... I have windows firewall disabled but have Trend
Micro PC-cillin Internet Security 2005 with a firewall enabled and I took
steps to make sure it was setup proper but I could be wrong. I will also
mention now that both computers can see each other in network neighbourhood
and that they can access each others files. I believe when I was setting up
the firewall settings in Trend Micro I messed up the ip for the NVIDIA nForce
controller, I tried to locate the gateway IP addy and MAC addy with the find
feature and it came up with nothing and after that the adapter said it has a
"Manually Configured" IP of 192.168.0.1 (I believe it was different before).

I'll mention now that I'm also running XP home on both systems with service
pack 2 and I have ran the network setup wizzard on both machines successfully.
I have tried pinging both systems and my main pc says "Request timed out"
and the second pc says "Destination host unreachable" to both adapters (I
figured I would try pinging both adapters since they both have separate
IP's). I'll also list now what the ipconfig /all yielded for me.


<SNIP>

Also when I try to connect with the second PC it asks me to use dialup (it's
installed or was installed by the Sympatico software as a backup way to
connect if DSL failed for emergencies). I should have mentioned this earlier
too but the Network adapter on the second PC says that there is little or no
connectivity. Prior to messing around with my network I have now, I was
networked with my brothers laptop and it was fine except we couldn't see
eachother in lan games (could be game related) but everything else looked
A'ok. Because I couldn't see him in a lan game tho I got him to install
service pack 2 because I thought this might be the issue and it made it so he
too had limited or no connectivity to me. I tried to resolve that issue
myself but gave up and am now working on my own setup. I mentioned the
sevice pack 2 issue with the laptop to maybe show a connection with that and
my two PC's since both had little or no connectivinty with my comp but could
still access the network. Also the conectivity on my end has always seemed
fine (host PC)

I know all this is an aweful lot of info but I didn't know what was
pertinant and what wasn't, I'm sorry if it's long winded also :-( but I
always hated grammar.
I really hope someone can help and if I missed anything let me know?

Also what's a tunnel adapter?

Teredo Tunneling (which uses a tunnel adapter) is Microsoft providing IPV6 on a
native IPV4 platform. Some folks claim that IPV6 and Windows Networking
(browsing / file sharing) works fine with IPV6. My experience is if you have
problems, the first thing to do is to remove it from both computers. Get file
sharing working, then add it back and see if file sharing works.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Thanks Chuck, but now I need to know or rather I'm curious what a tunnel
adapter is lol!

I'm not sure if you were thinking that was my problem, but I'm pretty sure
it's not (but I really don't know) because File sharing has never been the
problem, I have always been able to share files even tho I had no
connectivity.

But I really appreciate the info I'm so interested in all this I simply love
computers, it just frustrates the *poo* out of me when I can get something to
work but I don't give up (sigh).

Windows Networking (file sharing), and Internet access, uses TCP/IP (with "IP"
being IPV4). IPV4 uses IP addresses with the format nnn.nnn.nnn.nnn. TCP/IP
(IPV4) and NetBIOS Over TCP/IP, is the default and supported transport for
Windows XP, and most preceding Windows versions.

Tunneling is the process of letting an application, running on your native IPV4
computer, communicate with a host that uses only IPV6. The IPV6 communications
"tunnel" thru IPV4 to the distant IPV6 network and host.

Teredo Tunneling, and IPV6, are supposed to be transparent to NetBIOS Over
TCP/IP. In cases like yours, this may not be the case. Many times, folks like
you have written here describing problems like yours. In most cases, removal of
IPV6 is essential to resolution of their problems. Google in this forum, if you
don't believe me.
<http://groups.google.com/group/microsoft.public.windowsxp.network_web/search?q=IPV6&start=0&scoring=d&;>
http://groups.google.com/group/microsoft.public.windowsxp.network_web/search?q=IPV6&start=0&scoring=d&;

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

.

Relevant Pages

  • Re: ISA 2004 - Microsoft Firewall Event ID 14147
    ... Are you running any kind of PPPoE software on your server? ... Connection-specific DNS Suffix. ... Ethernet adapter 3COM NIC for BellSouth DSL: ... > with the network element to which this adapter belongs. ...
    (microsoft.public.windows.server.sbs)
  • Host of networking problems ...
    ... I have been working several hours now on my network problem and have gotten ... is listed as 1394 Net Adapter and is disabled) and I have a gateway that I'm ... Connection-specific DNS Suffix. ... Tunnel adapter Automatic Tunneling Pseudo-Interface: ...
    (microsoft.public.windowsxp.network_web)
  • Re: ISA 2004 - Microsoft Firewall Event ID 14147
    ... Connection-specific DNS Suffix. ... Ethernet adapter 3COM NIC for BellSouth DSL: ... ISA Server detected routes through adapter Loopback that do not correlate ... with the network element to which this adapter belongs. ...
    (microsoft.public.windows.server.sbs)
  • Re: Host of networking problems ...
    ... I have been working several hours now on my network problem and have gotten ... is listed as 1394 Net Adapter and is disabled) and I have a gateway that I'm ... Connection-specific DNS Suffix. ... Tunnel adapter Automatic Tunneling Pseudo-Interface: ...
    (microsoft.public.windowsxp.network_web)
  • Re: Its me again - network only works with Windows ME
    ... My network worked fine until a virus attack on both XP machines. ... Connection-specific DNS Suffix. ... Tunnel adapter Automatic Tunneling Pseudo-Interface: ... computers, it's generally most useful to provide diagnostic data, like "ipconfig ...
    (microsoft.public.windowsxp.network_web)