Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Tue, 04 Feb 2003 11:48:44



Hi,

I have had this problem for a long time now and I still have had no
solution, I'm hoping that someone may now be able to help.

The situation:
Windows XP Pro SP1 - ICS Host
Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.

Now, the following is true:
1. The Windows 2000 machine USED to connect.  Slowly, program by program, it
would stop connecting.  Now the vast majority of programs will not connect
(including all the Microsoft apps - strangely, WinAmp DOES).  Nothing at all
has changed that would affect the network in any way.
2. A Windows 95 OSR2.1 host connects with no problems.
3. A Windows 98SE host connects with no problems.
4. Any other XP machines that are introduced to the network connect with no
problems.
5. All of the clients are set up exactly the same.
6. This happened before I installed the IPv6 drivers, so IPv6 is not causing
the problems.
7. All machines have all available updates installed.

The following is all the information I can think to give anyone who may be
able to help, I would zip this information but I know some newsreaders dump
messages with attachments.

--| WINDOWS 2000 "IPCONFIG/ALL" |--

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : Win2K
        Primary DNS Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Mixed
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Home:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC
(3C
905-TX)
        Physical Address. . . . . . . . . : 00-60-08-10-45-BA
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.2
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 192.168.0.1
        Primary WINS Server . . . . . . . : 192.168.0.1

--| WINDOWS 2000 "NETSTAT -AN"  |--

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
  TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
  TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1036           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1038           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2774           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2792           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3372           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:6555         0.0.0.0:0              LISTENING
  TCP    192.168.0.2:23         192.168.0.1:3093       ESTABLISHED
  TCP    192.168.0.2:139        0.0.0.0:0              LISTENING
  TCP    192.168.0.2:139        192.168.0.1:3021       ESTABLISHED
  TCP    192.168.0.2:2774       192.168.0.1:1504       ESTABLISHED
  TCP    192.168.0.2:2775       0.0.0.0:0              LISTENING
  TCP    192.168.0.2:2784       0.0.0.0:0              LISTENING
  TCP    192.168.0.2:2784       192.168.0.1:139        ESTABLISHED
  TCP    192.168.0.2:2792       192.168.0.1:1999       ESTABLISHED
  UDP    0.0.0.0:7              *:*
  UDP    0.0.0.0:9              *:*
  UDP    0.0.0.0:13             *:*
  UDP    0.0.0.0:17             *:*
  UDP    0.0.0.0:19             *:*
  UDP    0.0.0.0:135            *:*
  UDP    0.0.0.0:161            *:*
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:1037           *:*
  UDP    0.0.0.0:1040           *:*
  UDP    0.0.0.0:3456           *:*
  UDP    0.0.0.0:3527           *:*
  UDP    0.0.0.0:38037          *:*
  UDP    192.168.0.2:137        *:*
  UDP    192.168.0.2:138        *:*
  UDP    192.168.0.2:500        *:*
  UDP    192.168.0.2:520        *:*

--|  WINDOWS 2000 "ROUTE PRINT"  |--

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 60 08 10 45 ba ...... 3Com 3C90x Ethernet Adapter (Microsoft's
Packet
Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.2       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.0.0    255.255.255.0      192.168.0.2     192.168.0.2       1
      192.168.0.2  255.255.255.255        127.0.0.1       127.0.0.1       1
    192.168.0.255  255.255.255.255      192.168.0.2     192.168.0.2       1
        224.0.0.0        224.0.0.0      192.168.0.2     192.168.0.2       1
  255.255.255.255  255.255.255.255      192.168.0.2     192.168.0.2       1
Default Gateway:       192.168.0.1
===========================================================================
Persistent Routes:
  None

--|  WINDOWS XP "IPCONFIG/ALL"  |--

Windows IP Configuration

        Host Name . . . . . . . . . . . . : WinXP
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : Yes
        WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Home:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet
Controller (3C905C-TX Compatible)
        Physical Address. . . . . . . . . : 00-B0-D0-A4-5C-20
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : 2002:c0a8:1:4:1db2:6cde:23a7:1d0
        IP Address. . . . . . . . . . . . : 2002:c0a8:1:4:2b0:d0ff:fea4:5c20
        IP Address. . . . . . . . . . . . : fe80::2b0:d0ff:fea4:5c20%4
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1

--|  WINDOWS XP "NETSTAT -AON"  |--

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1476
  TCP    0.0.0.0:23             0.0.0.0:0              LISTENING       300
  TCP    0.0.0.0:59             0.0.0.0:0              LISTENING       760
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       1476
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       860
  TCP    0.0.0.0:251            0.0.0.0:0              LISTENING       968
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       1476
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:1024           0.0.0.0:0              LISTENING       3492
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       968
  TCP    0.0.0.0:1027           0.0.0.0:0              LISTENING       1536
  TCP    0.0.0.0:1030           0.0.0.0:0              LISTENING       1476
  TCP    0.0.0.0:1033           0.0.0.0:0              LISTENING       940
  TCP    0.0.0.0:1034           0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:1080           0.0.0.0:0              LISTENING       1936
  TCP    0.0.0.0:1504           0.0.0.0:0              LISTENING       224
  TCP    0.0.0.0:1505           0.0.0.0:0              LISTENING       224
  TCP    0.0.0.0:1506           0.0.0.0:0              LISTENING       224
  TCP    0.0.0.0:1723           0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING       940
  TCP    0.0.0.0:1999           0.0.0.0:0              LISTENING       396
  TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING       940
  TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING       940
  TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING       940
  TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING       1196
  TCP    0.0.0.0:3023           0.0.0.0:0              LISTENING       1196
  TCP    0.0.0.0:3026           0.0.0.0:0              LISTENING       1744
  TCP    0.0.0.0:3033           0.0.0.0:0              LISTENING       1196
  TCP    0.0.0.0:3034           0.0.0.0:0              LISTENING       4048
  TCP    0.0.0.0:3049           0.0.0.0:0              LISTENING       1196
  TCP    0.0.0.0:3123           0.0.0.0:0              LISTENING       1196
  TCP    0.0.0.0:3124           0.0.0.0:0              LISTENING       1196
  TCP    0.0.0.0:3127           0.0.0.0:0              LISTENING       3380
  TCP    0.0.0.0:3137           0.0.0.0:0              LISTENING       3572
  TCP    0.0.0.0:3147           0.0.0.0:0              LISTENING      
...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by Robert » Tue, 04 Feb 2003 12:59:38


could you also please post pathping yahoo.com from w2k?

--
For more information, go to  http://www25.brinkster.com/ChicagoTech

Please don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, CNE & MCSE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.

"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:uJNp16yyCHA.2332@TK2MSFTNGP09...
> Hi,

> I have had this problem for a long time now and I still have had no
> solution, I'm hoping that someone may now be able to help.

> The situation:
> Windows XP Pro SP1 - ICS Host
> Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.

> Now, the following is true:
> 1. The Windows 2000 machine USED to connect.  Slowly, program by program,
it
> would stop connecting.  Now the vast majority of programs will not connect
> (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing at
all
> has changed that would affect the network in any way.
> 2. A Windows 95 OSR2.1 host connects with no problems.
> 3. A Windows 98SE host connects with no problems.
> 4. Any other XP machines that are introduced to the network connect with
no
> problems.
> 5. All of the clients are set up exactly the same.
> 6. This happened before I installed the IPv6 drivers, so IPv6 is not
causing
> the problems.
> 7. All machines have all available updates installed.

> The following is all the information I can think to give anyone who may be
> able to help, I would zip this information but I know some newsreaders
dump
> messages with attachments.

> --| WINDOWS 2000 "IPCONFIG/ALL" |--

> Windows 2000 IP Configuration

>         Host Name . . . . . . . . . . . . : Win2K
>         Primary DNS Suffix  . . . . . . . :
>         Node Type . . . . . . . . . . . . : Mixed
>         IP Routing Enabled. . . . . . . . : No
>         WINS Proxy Enabled. . . . . . . . : No

> Ethernet adapter Home:

>         Connection-specific DNS Suffix  . :
>         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
NIC
> (3C
> 905-TX)
>         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
>         DHCP Enabled. . . . . . . . . . . : No
>         IP Address. . . . . . . . . . . . : 192.168.0.2
>         Subnet Mask . . . . . . . . . . . : 255.255.255.0
>         Default Gateway . . . . . . . . . : 192.168.0.1
>         DNS Servers . . . . . . . . . . . : 192.168.0.1
>         Primary WINS Server . . . . . . . : 192.168.0.1

> --| WINDOWS 2000 "NETSTAT -AN"  |--

> Active Connections

>   Proto  Local Address          Foreign Address        State
>   TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1036           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1038           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:2774           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:2792           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:3372           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:6555         0.0.0.0:0              LISTENING
>   TCP    192.168.0.2:23         192.168.0.1:3093       ESTABLISHED
>   TCP    192.168.0.2:139        0.0.0.0:0              LISTENING
>   TCP    192.168.0.2:139        192.168.0.1:3021       ESTABLISHED
>   TCP    192.168.0.2:2774       192.168.0.1:1504       ESTABLISHED
>   TCP    192.168.0.2:2775       0.0.0.0:0              LISTENING
>   TCP    192.168.0.2:2784       0.0.0.0:0              LISTENING
>   TCP    192.168.0.2:2784       192.168.0.1:139        ESTABLISHED
>   TCP    192.168.0.2:2792       192.168.0.1:1999       ESTABLISHED
>   UDP    0.0.0.0:7              *:*
>   UDP    0.0.0.0:9              *:*
>   UDP    0.0.0.0:13             *:*
>   UDP    0.0.0.0:17             *:*
>   UDP    0.0.0.0:19             *:*
>   UDP    0.0.0.0:135            *:*
>   UDP    0.0.0.0:161            *:*
>   UDP    0.0.0.0:445            *:*
>   UDP    0.0.0.0:1037           *:*
>   UDP    0.0.0.0:1040           *:*
>   UDP    0.0.0.0:3456           *:*
>   UDP    0.0.0.0:3527           *:*
>   UDP    0.0.0.0:38037          *:*
>   UDP    192.168.0.2:137        *:*
>   UDP    192.168.0.2:138        *:*
>   UDP    192.168.0.2:500        *:*
>   UDP    192.168.0.2:520        *:*

> --|  WINDOWS 2000 "ROUTE PRINT"  |--

===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 60 08 10 45 ba ...... 3Com 3C90x Ethernet Adapter (Microsoft's
> Packet
> Scheduler)

===========================================================================

===========================================================================

- Show quoted text -

> Active Routes:
> Network Destination        Netmask          Gateway       Interface
Metric
>           0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.2
1
>         127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1
1
>       192.168.0.0    255.255.255.0      192.168.0.2     192.168.0.2
1
>       192.168.0.2  255.255.255.255        127.0.0.1       127.0.0.1
1
>     192.168.0.255  255.255.255.255      192.168.0.2     192.168.0.2
1
>         224.0.0.0        224.0.0.0      192.168.0.2     192.168.0.2
1
>   255.255.255.255  255.255.255.255      192.168.0.2     192.168.0.2
1
> Default Gateway:       192.168.0.1

===========================================================================

- Show quoted text -

> Persistent Routes:
>   None

> --|  WINDOWS XP "IPCONFIG/ALL"  |--

> Windows IP Configuration

>         Host Name . . . . . . . . . . . . : WinXP
>         Primary Dns Suffix  . . . . . . . :
>         Node Type . . . . . . . . . . . . : Unknown
>         IP Routing Enabled. . . . . . . . : Yes
>         WINS Proxy Enabled. . . . . . . . : Yes

> Ethernet adapter Home:

>         Connection-specific DNS Suffix  . :
>         Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
> Ethernet
> Controller (3C905C-TX Compatible)
>         Physical Address. . . . . . . . . : 00-B0-D0-A4-5C-20
>         Dhcp Enabled. . . . . . . . . . . : No
>         IP Address. . . . . . . . . . . . : 192.168.0.1
>         Subnet Mask . . . . . . . . . . . : 255.255.255.0
>         IP Address. . . . . . . . . . . . :

2002:c0a8:1:4:1db2:6cde:23a7:1d0
>         IP Address. . . . . . . . . . . . :

2002:c0a8:1:4:2b0:d0ff:fea4:5c20

- Show quoted text -

>         IP Address. . . . . . . . . . . . : fe80::2b0:d0ff:fea4:5c20%4
>         Default Gateway . . . . . . . . . :
>         DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
>                                             fec0:0:0:ffff::2%1
>                                             fec0:0:0:ffff::3%1

> --|  WINDOWS XP "NETSTAT -AON"  |--

> Active Connections

>   Proto  Local Address          Foreign Address        State           PID
>   TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
1476
>   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING       300
>   TCP    0.0.0.0:59             0.0.0.0:0              LISTENING       760
>   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
1476
>   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       860
>   TCP    0.0.0.0:251            0.0.0.0:0              LISTENING       968
>   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
1476
>   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
>   TCP    0.0.0.0:1024           0.0.0.0:0              LISTENING
3492
>   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       968
>   TCP    0.0.0.0:1027           0.0.0.0:0              LISTENING
1536
>   TCP    0.0.0.0:1030           0.0.0.0:0              LISTENING
1476
>   TCP    0.0.0.0:1033           0.0.0.0:0              LISTENING       940
>   TCP    0.0.0.0:1034           0.0.0.0:0              LISTENING       4
>   TCP    0.0.0.0:1080           0.0.0.0:0              LISTENING
1936
>   TCP    0.0.0.0:1504           0.0.0.0:0              LISTENING       224
>   TCP    0.0.0.0:1505           0.0.0.0:0              LISTENING       224
>   TCP    0.0.0.0:1506           0.0.0.0:0              LISTENING       224
>   TCP    0.0.0.0:1723           0.0.0.0:0              LISTENING       4
>   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING       940
>   TCP    0.0.0.0:1999           0.0.0.0:0              LISTENING       396
>   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING       940
>   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING       940
>   TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING       940
>   TCP  

...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Tue, 04 Feb 2003 22:57:40


Sure can :)

--|  WIN 2000 "PATHPING YAHOO.COM"  |--

Tracing route to yahoo.com [64.58.79.230]

over a maximum of 30 hops:

  0  win2k [192.168.0.2]

  1  WinXP.mshome.net [192.168.0.1]

  2  vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]

  3  192.168.253.2

  4  172.16.56.177

  5  172.16.50.133

  6  172.16.50.7

  7  213.121.156.21

  8  core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]

  9  core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]

 10  core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]

 11  core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]

 12  transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]

 13  transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]

 14  exchange-cust1.ash.equinix.net [206.223.115.16]

 15  ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]

 16  vl43.bas1.dcx.yahoo.com [216.109.120.190]

 17

Computing statistics for 425 seconds...

            Source to Here   This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                           win2k [192.168.0.2]

                                0/ 100 =  0%   |

  1    0ms     0/ 100 =  0%     0/ 100 =  0%  WinXP.mshome.net [192.168.0.1]

                              100/ 100 =100%   |

  2  ---     100/ 100 =100%     0/ 100 =  0%
vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]

                                0/ 100 =  0%   |

  3  ---     100/ 100 =100%     0/ 100 =  0%  192.168.253.2

                                0/ 100 =  0%   |

  4  ---     100/ 100 =100%     0/ 100 =  0%  172.16.56.177

                                0/ 100 =  0%   |

  5  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.133

                                0/ 100 =  0%   |

  6  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.7

                                0/ 100 =  0%   |

  7  ---     100/ 100 =100%     0/ 100 =  0%  213.121.156.21

                                0/ 100 =  0%   |

  8  ---     100/ 100 =100%     0/ 100 =  0%
core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]

                                0/ 100 =  0%   |

  9  ---     100/ 100 =100%     0/ 100 =  0%
core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]

                                0/ 100 =  0%   |

 10  ---     100/ 100 =100%     0/ 100 =  0%
core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]

                                0/ 100 =  0%   |

 11  ---     100/ 100 =100%     0/ 100 =  0%
core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]

                                0/ 100 =  0%   |

 12  ---     100/ 100 =100%     0/ 100 =  0%
transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]

                                0/ 100 =  0%   |

 13  ---     100/ 100 =100%     0/ 100 =  0%
transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]

                                0/ 100 =  0%   |

 14  ---     100/ 100 =100%     0/ 100 =  0%  exchange-cust1.ash.equinix.net
[206.223.115.16]

                                0/ 100 =  0%   |

 15  ---     100/ 100 =100%     0/ 100 =  0%
ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]

                                0/ 100 =  0%   |

 16  ---     100/ 100 =100%     0/ 100 =  0%  vl43.bas1.dcx.yahoo.com
[216.109.120.190]

                                0/ 100 =  0%   |

 17  ---     100/ 100 =100%     0/ 100 =  0%  Ken [0.0.0.0]

Trace complete.

...

--|  WIN 2000 "TRACERT YAHOO.COM"  |--

Tracing route to yahoo.com [64.58.79.230]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  WinXP.mshome.net [192.168.0.1]
  2   180 ms   200 ms   191 ms  vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net
[213.
121.147.68]
  3   180 ms   191 ms   190 ms  192.168.253.2
  4   170 ms   191 ms   180 ms  172.16.56.177
  5   180 ms   180 ms   181 ms  172.16.50.133
  6   180 ms   240 ms   190 ms  172.16.50.8
  7   161 ms   180 ms   180 ms  213.121.156.25
  8   170 ms   181 ms   170 ms  core2-gig3-0.rochdale.ukcore.bt.net
[217.32.168.
66]
  9   171 ms   170 ms   170 ms  core2-pos5-1.birmingham.ukcore.bt.net
[194.74.16
.193]
 10   170 ms   160 ms   170 ms  core2-pos13-2.reading.ukcore.bt.net
[62.6.196.11
0]
 11   180 ms   190 ms   171 ms  core2-pos13-1.ealing.ukcore.bt.net
[62.6.196.242
]
 12   170 ms   181 ms   190 ms  transit1-pos4-0.ealing.ukcore.bt.net
[194.72.9.2
38]
 13   250 ms   250 ms   251 ms  transit2-pos8-0.washington.ukcore.bt.net
[194.72
.9.14]
 14   270 ms   261 ms   270 ms  exchange-cust1.ash.equinix.net
[206.223.115.16]

 15   261 ms   270 ms   260 ms  ge-0-3-0-p34.msr1.dcn.yahoo.com
[216.109.120.161
]
 16     *      281 ms     *     vl43.bas1.dcx.yahoo.com [216.109.120.190]
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *     ^C

I never asked for the ".mshome.net" but I don't know how to get rid of it.
:-(

Cheers.

"Robert L" <bobli...@hotmail.com> wrote in message

news:eTXWoizyCHA.2232@TK2MSFTNGP11...
: could you also please post pathping yahoo.com from w2k?
:
: --
: For more information, go to  http://www25.brinkster.com/ChicagoTech
:
: Please don't send e-mail or reply to me except you need consulting
services.
: Posting on MS newsgroup will benefit all readers and you may get more
help.
:
: Robert Lin, CNE & MCSE
: Windows & Network Support, Tips and FAQs on
: http://www25.brinkster.com/ChicagoTech
: This posting is provided "AS IS" with no warranties.
:
: "QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

: news:uJNp16yyCHA.2332@TK2MSFTNGP09...
: > Hi,
: >
: > I have had this problem for a long time now and I still have had no
: > solution, I'm hoping that someone may now be able to help.
: >
: > The situation:
: > Windows XP Pro SP1 - ICS Host
: > Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
: >
: > Now, the following is true:
: > 1. The Windows 2000 machine USED to connect.  Slowly, program by
program,
: it
: > would stop connecting.  Now the vast majority of programs will not
connect
: > (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing at
: all
: > has changed that would affect the network in any way.
: > 2. A Windows 95 OSR2.1 host connects with no problems.
: > 3. A Windows 98SE host connects with no problems.
: > 4. Any other XP machines that are introduced to the network connect with
: no
: > problems.
: > 5. All of the clients are set up exactly the same.
: > 6. This happened before I installed the IPv6 drivers, so IPv6 is not
: causing
: > the problems.
: > 7. All machines have all available updates installed.
: >
: > The following is all the information I can think to give anyone who may
be
: > able to help, I would zip this information but I know some newsreaders
: dump
: > messages with attachments.
: >
: >
: > --| WINDOWS 2000 "IPCONFIG/ALL" |--
: >
: > Windows 2000 IP Configuration
: >
: >         Host Name . . . . . . . . . . . . : Win2K
: >         Primary DNS Suffix  . . . . . . . :
: >         Node Type . . . . . . . . . . . . : Mixed
: >         IP Routing Enabled. . . . . . . . : No
: >         WINS Proxy Enabled. . . . . . . . : No
: >
: > Ethernet adapter Home:
: >
: >         Connection-specific DNS Suffix  . :
: >         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
: NIC
: > (3C
: > 905-TX)
: >         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
: >         DHCP Enabled. . . . . . . . . . . : No
: >         IP Address. . . . . . . . . . . . : 192.168.0.2
: >         Subnet Mask . . . . . . . . . . . : 255.255.255.0
: >         Default Gateway . . . . . . . . . : 192.168.0.1
: >         DNS Servers . . . . . . . . . . . : 192.168.0.1
: >         Primary WINS Server . . . . . . . : 192.168.0.1
: >
: >
: > --| WINDOWS 2000 "NETSTAT -AN"  |--
: >
: > Active Connections
: >
: >   Proto  Local Address          Foreign Address        State
: >   TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:1036           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:1038           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:2774           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:2792           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:3372           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING
: >   TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING
: >   TCP    127.0.0.1:6555         0.0.0.0:0              LISTENING
: >   TCP    192.168.0.2:23         192.168.0.1:3093       ESTABLISHED
: >   TCP    192.168.0.2:139        0.0.0.0:0              LISTENING
: >   TCP    192.168.0.2:139        192.168.0.1:3021       ESTABLISHED
: >   TCP    192.168.0.2:2774       192.168.0.1:1504       ESTABLISHED
: >   TCP    192.168.0.2:2775       0.0.0.0:0              LISTENING
...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by Robert » Tue, 04 Feb 2003 23:36:21


Perhaps, w2k is connecting the Internet and the problem is IE, for example,
make sure no LAN settings. what do you get when access a web site? the only
question I have is why tracert was time out after vl43.bas1.dcx.yahoo.com
[216.109.120.190]. It should be Trace complete.

--
For more information, go to  http://www25.brinkster.com/ChicagoTech

Please don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, CNE & MCSE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.

"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:ezeOpw4yCHA.1900@TK2MSFTNGP10...
> Sure can :)

> --|  WIN 2000 "PATHPING YAHOO.COM"  |--

> Tracing route to yahoo.com [64.58.79.230]

> over a maximum of 30 hops:

>   0  win2k [192.168.0.2]

>   1  WinXP.mshome.net [192.168.0.1]

>   2  vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]

>   3  192.168.253.2

>   4  172.16.56.177

>   5  172.16.50.133

>   6  172.16.50.7

>   7  213.121.156.21

>   8  core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]

>   9  core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]

>  10  core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]

>  11  core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]

>  12  transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]

>  13  transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]

>  14  exchange-cust1.ash.equinix.net [206.223.115.16]

>  15  ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]

>  16  vl43.bas1.dcx.yahoo.com [216.109.120.190]

>  17

> Computing statistics for 425 seconds...

>             Source to Here   This Node/Link

> Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

>   0                                           win2k [192.168.0.2]

>                                 0/ 100 =  0%   |

>   1    0ms     0/ 100 =  0%     0/ 100 =  0%  WinXP.mshome.net
[192.168.0.1]

>                               100/ 100 =100%   |

>   2  ---     100/ 100 =100%     0/ 100 =  0%
> vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]

>                                 0/ 100 =  0%   |

>   3  ---     100/ 100 =100%     0/ 100 =  0%  192.168.253.2

>                                 0/ 100 =  0%   |

>   4  ---     100/ 100 =100%     0/ 100 =  0%  172.16.56.177

>                                 0/ 100 =  0%   |

>   5  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.133

>                                 0/ 100 =  0%   |

>   6  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.7

>                                 0/ 100 =  0%   |

>   7  ---     100/ 100 =100%     0/ 100 =  0%  213.121.156.21

>                                 0/ 100 =  0%   |

>   8  ---     100/ 100 =100%     0/ 100 =  0%
> core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]

>                                 0/ 100 =  0%   |

>   9  ---     100/ 100 =100%     0/ 100 =  0%
> core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]

>                                 0/ 100 =  0%   |

>  10  ---     100/ 100 =100%     0/ 100 =  0%
> core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]

>                                 0/ 100 =  0%   |

>  11  ---     100/ 100 =100%     0/ 100 =  0%
> core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]

>                                 0/ 100 =  0%   |

>  12  ---     100/ 100 =100%     0/ 100 =  0%
> transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]

>                                 0/ 100 =  0%   |

>  13  ---     100/ 100 =100%     0/ 100 =  0%
> transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]

>                                 0/ 100 =  0%   |

>  14  ---     100/ 100 =100%     0/ 100 =  0%

exchange-cust1.ash.equinix.net

- Show quoted text -

> [206.223.115.16]

>                                 0/ 100 =  0%   |

>  15  ---     100/ 100 =100%     0/ 100 =  0%
> ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]

>                                 0/ 100 =  0%   |

>  16  ---     100/ 100 =100%     0/ 100 =  0%  vl43.bas1.dcx.yahoo.com
> [216.109.120.190]

>                                 0/ 100 =  0%   |

>  17  ---     100/ 100 =100%     0/ 100 =  0%  Ken [0.0.0.0]

> Trace complete.

> ...

> --|  WIN 2000 "TRACERT YAHOO.COM"  |--

> Tracing route to yahoo.com [64.58.79.230]
> over a maximum of 30 hops:

>   1   <10 ms   <10 ms   <10 ms  WinXP.mshome.net [192.168.0.1]
>   2   180 ms   200 ms   191 ms  vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net
> [213.
> 121.147.68]
>   3   180 ms   191 ms   190 ms  192.168.253.2
>   4   170 ms   191 ms   180 ms  172.16.56.177
>   5   180 ms   180 ms   181 ms  172.16.50.133
>   6   180 ms   240 ms   190 ms  172.16.50.8
>   7   161 ms   180 ms   180 ms  213.121.156.25
>   8   170 ms   181 ms   170 ms  core2-gig3-0.rochdale.ukcore.bt.net
> [217.32.168.
> 66]
>   9   171 ms   170 ms   170 ms  core2-pos5-1.birmingham.ukcore.bt.net
> [194.74.16
> .193]
>  10   170 ms   160 ms   170 ms  core2-pos13-2.reading.ukcore.bt.net
> [62.6.196.11
> 0]
>  11   180 ms   190 ms   171 ms  core2-pos13-1.ealing.ukcore.bt.net
> [62.6.196.242
> ]
>  12   170 ms   181 ms   190 ms  transit1-pos4-0.ealing.ukcore.bt.net
> [194.72.9.2
> 38]
>  13   250 ms   250 ms   251 ms  transit2-pos8-0.washington.ukcore.bt.net
> [194.72
> .9.14]
>  14   270 ms   261 ms   270 ms  exchange-cust1.ash.equinix.net
> [206.223.115.16]

>  15   261 ms   270 ms   260 ms  ge-0-3-0-p34.msr1.dcn.yahoo.com
> [216.109.120.161
> ]
>  16     *      281 ms     *     vl43.bas1.dcx.yahoo.com [216.109.120.190]
>  17     *        *        *     Request timed out.
>  18     *        *        *     Request timed out.
>  19     *        *        *     Request timed out.
>  20     *        *        *     Request timed out.
>  21     *        *     ^C

> I never asked for the ".mshome.net" but I don't know how to get rid of it.
> :-(

> Cheers.

> "Robert L" <bobli...@hotmail.com> wrote in message
> news:eTXWoizyCHA.2232@TK2MSFTNGP11...
> : could you also please post pathping yahoo.com from w2k?
> :
> : --
> : For more information, go to  http://www25.brinkster.com/ChicagoTech
> :
> : Please don't send e-mail or reply to me except you need consulting
> services.
> : Posting on MS newsgroup will benefit all readers and you may get more
> help.
> :
> : Robert Lin, CNE & MCSE
> : Windows & Network Support, Tips and FAQs on
> : http://www25.brinkster.com/ChicagoTech
> : This posting is provided "AS IS" with no warranties.
> :
> : "QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message
> : news:uJNp16yyCHA.2332@TK2MSFTNGP09...
> : > Hi,
> : >
> : > I have had this problem for a long time now and I still have had no
> : > solution, I'm hoping that someone may now be able to help.
> : >
> : > The situation:
> : > Windows XP Pro SP1 - ICS Host
> : > Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
> : >
> : > Now, the following is true:
> : > 1. The Windows 2000 machine USED to connect.  Slowly, program by
> program,
> : it
> : > would stop connecting.  Now the vast majority of programs will not
> connect
> : > (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing
at
> : all
> : > has changed that would affect the network in any way.
> : > 2. A Windows 95 OSR2.1 host connects with no problems.
> : > 3. A Windows 98SE host connects with no problems.
> : > 4. Any other XP machines that are introduced to the network connect
with
> : no
> : > problems.
> : > 5. All of the clients are set up exactly the same.
> : > 6. This happened before I installed the IPv6 drivers, so IPv6 is not
> : causing
> : > the problems.
> : > 7. All machines have all available updates installed.
> : >
> : > The following is all the information I can think to give anyone who
may
> be
> : > able to help, I would zip this information but I know some newsreaders
> : dump
> : > messages with attachments.
> : >
> : >
> : > --| WINDOWS 2000 "IPCONFIG/ALL" |--
> : >
> : > Windows 2000 IP Configuration
> : >
> : >         Host Name . . . . . . . . . . . . : Win2K
> : >         Primary DNS Suffix  . . . . . . . :
> : >         Node Type . . . . . . . . . . . . : Mixed
> : >         IP Routing Enabled. . . . . . . . : No
> : >         WINS Proxy Enabled. . . . . . . . : No
> : >
> : > Ethernet adapter Home:
> : >
> : >         Connection-specific DNS Suffix  . :
> : >         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
> : NIC
> : > (3C
> : > 905-TX)
> : >         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
> : >         DHCP Enabled. . . . . . . . . . . : No
> : >         IP Address. . . . . . . . . . . . : 192.168.0.2
> : >         Subnet Mask . . . . . . . . . . . : 255.255.255.0
> : >         Default Gateway . . . . . . . . . : 192.168.0.1
> : >         DNS Servers . . . . . . . . . . . : 192.168.0.1
> : >         Primary WINS Server . . . . . . . : 192.168.0.1
> : >
> : >
> : > --| WINDOWS 2000 "NETSTAT -AN"  |--
> : >
> : > Active Connections
> : >
> : >   Proto  Local Address          Foreign Address        State
> : >   TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
> : >   TCP    0.0.0.0:1026           0.0.0.0:0        

...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Wed, 05 Feb 2003 00:08:58


I get a PAGE NOT FOUND or UNABLE TO DISPLAY DOCUMENT etcetera.
The DNS is obviously working as it can resolve IPs to their host names and
vice versa.
I don't know what you mean by make sure no LAN settings. :-/

As I said earlier, Microsoft apps do not connect to the Internet, but
WinAmp, for example, will.
Java will not either.

So they both have something in common that is making them unable to connect,
whereas WinAmp is obviously getting around this problem.  (WinAmp has a
minibrowser and can connect to the CDDB without any problems).


: Perhaps, w2k is connecting the Internet and the problem is IE, for
example,
: make sure no LAN settings. what do you get when access a web site? the
only
: question I have is why tracert was time out after vl43.bas1.dcx.yahoo.com
: [216.109.120.190]. It should be Trace complete.
:
:
: --
: For more information, go to  http://www25.brinkster.com/ChicagoTech
:
: Please don't send e-mail or reply to me except you need consulting
services.
: Posting on MS newsgroup will benefit all readers and you may get more
help.
:
: Robert Lin, CNE & MCSE
: Windows & Network Support, Tips and FAQs on
: http://www25.brinkster.com/ChicagoTech
: This posting is provided "AS IS" with no warranties.

<snip>

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Wed, 05 Feb 2003 09:36:06


The DNS proxy agent was unable to read the local list of name-resolution
servers from the registry. The data is the error code.

From the Event Log, will this have anything to do with it?

"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:ezeOpw4yCHA.1900@TK2MSFTNGP10...
: Sure can :)
:
: --|  WIN 2000 "PATHPING YAHOO.COM"  |--
:
:
:
: Tracing route to yahoo.com [64.58.79.230]
:
: over a maximum of 30 hops:
:
:   0  win2k [192.168.0.2]
:
:   1  WinXP.mshome.net [192.168.0.1]
:
:   2  vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]
:
:   3  192.168.253.2
:
:   4  172.16.56.177
:
:   5  172.16.50.133
:
:   6  172.16.50.7
:
:   7  213.121.156.21
:
:   8  core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]
:
:   9  core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]
:
:  10  core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]
:
:  11  core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]
:
:  12  transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]
:
:  13  transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]
:
:  14  exchange-cust1.ash.equinix.net [206.223.115.16]
:
:  15  ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]
:
:  16  vl43.bas1.dcx.yahoo.com [216.109.120.190]
:
:  17
:
: Computing statistics for 425 seconds...
:
:             Source to Here   This Node/Link
:
: Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
:
:   0                                           win2k [192.168.0.2]
:
:                                 0/ 100 =  0%   |
:
:   1    0ms     0/ 100 =  0%     0/ 100 =  0%  WinXP.mshome.net
[192.168.0.1]
:
:                               100/ 100 =100%   |
:
:   2  ---     100/ 100 =100%     0/ 100 =  0%
: vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]
:
:                                 0/ 100 =  0%   |
:
:   3  ---     100/ 100 =100%     0/ 100 =  0%  192.168.253.2
:
:                                 0/ 100 =  0%   |
:
:   4  ---     100/ 100 =100%     0/ 100 =  0%  172.16.56.177
:
:                                 0/ 100 =  0%   |
:
:   5  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.133
:
:                                 0/ 100 =  0%   |
:
:   6  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.7
:
:                                 0/ 100 =  0%   |
:
:   7  ---     100/ 100 =100%     0/ 100 =  0%  213.121.156.21
:
:                                 0/ 100 =  0%   |
:
:   8  ---     100/ 100 =100%     0/ 100 =  0%
: core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]
:
:                                 0/ 100 =  0%   |
:
:   9  ---     100/ 100 =100%     0/ 100 =  0%
: core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]
:
:                                 0/ 100 =  0%   |
:
:  10  ---     100/ 100 =100%     0/ 100 =  0%
: core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]
:
:                                 0/ 100 =  0%   |
:
:  11  ---     100/ 100 =100%     0/ 100 =  0%
: core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]
:
:                                 0/ 100 =  0%   |
:
:  12  ---     100/ 100 =100%     0/ 100 =  0%
: transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]
:
:                                 0/ 100 =  0%   |
:
:  13  ---     100/ 100 =100%     0/ 100 =  0%
: transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]
:
:                                 0/ 100 =  0%   |
:
:  14  ---     100/ 100 =100%     0/ 100 =  0%
exchange-cust1.ash.equinix.net
: [206.223.115.16]
:
:                                 0/ 100 =  0%   |
:
:  15  ---     100/ 100 =100%     0/ 100 =  0%
: ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]
:
:                                 0/ 100 =  0%   |
:
:  16  ---     100/ 100 =100%     0/ 100 =  0%  vl43.bas1.dcx.yahoo.com
: [216.109.120.190]
:
:                                 0/ 100 =  0%   |
:
:  17  ---     100/ 100 =100%     0/ 100 =  0%  Ken [0.0.0.0]
:
:
:
: Trace complete.
:
: ...
:
:
: --|  WIN 2000 "TRACERT YAHOO.COM"  |--
:
: Tracing route to yahoo.com [64.58.79.230]
: over a maximum of 30 hops:
:
:   1   <10 ms   <10 ms   <10 ms  WinXP.mshome.net [192.168.0.1]
:   2   180 ms   200 ms   191 ms  vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net
: [213.
: 121.147.68]
:   3   180 ms   191 ms   190 ms  192.168.253.2
:   4   170 ms   191 ms   180 ms  172.16.56.177
:   5   180 ms   180 ms   181 ms  172.16.50.133
:   6   180 ms   240 ms   190 ms  172.16.50.8
:   7   161 ms   180 ms   180 ms  213.121.156.25
:   8   170 ms   181 ms   170 ms  core2-gig3-0.rochdale.ukcore.bt.net
: [217.32.168.
: 66]
:   9   171 ms   170 ms   170 ms  core2-pos5-1.birmingham.ukcore.bt.net
: [194.74.16
: .193]
:  10   170 ms   160 ms   170 ms  core2-pos13-2.reading.ukcore.bt.net
: [62.6.196.11
: 0]
:  11   180 ms   190 ms   171 ms  core2-pos13-1.ealing.ukcore.bt.net
: [62.6.196.242
: ]
:  12   170 ms   181 ms   190 ms  transit1-pos4-0.ealing.ukcore.bt.net
: [194.72.9.2
: 38]
:  13   250 ms   250 ms   251 ms  transit2-pos8-0.washington.ukcore.bt.net
: [194.72
: .9.14]
:  14   270 ms   261 ms   270 ms  exchange-cust1.ash.equinix.net
: [206.223.115.16]
:
:  15   261 ms   270 ms   260 ms  ge-0-3-0-p34.msr1.dcn.yahoo.com
: [216.109.120.161
: ]
:  16     *      281 ms     *     vl43.bas1.dcx.yahoo.com [216.109.120.190]
:  17     *        *        *     Request timed out.
:  18     *        *        *     Request timed out.
:  19     *        *        *     Request timed out.
:  20     *        *        *     Request timed out.
:  21     *        *     ^C
:
:
:
: I never asked for the ".mshome.net" but I don't know how to get rid of it.
: :-(
:
: Cheers.
:
:
: "Robert L" <bobli...@hotmail.com> wrote in message
: news:eTXWoizyCHA.2232@TK2MSFTNGP11...
: : could you also please post pathping yahoo.com from w2k?
: :
: : --
: : For more information, go to  http://www25.brinkster.com/ChicagoTech
: :
: : Please don't send e-mail or reply to me except you need consulting
: services.
: : Posting on MS newsgroup will benefit all readers and you may get more
: help.
: :
: : Robert Lin, CNE & MCSE
: : Windows & Network Support, Tips and FAQs on
: : http://www25.brinkster.com/ChicagoTech
: : This posting is provided "AS IS" with no warranties.
: :
: : "QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message
: : news:uJNp16yyCHA.2332@TK2MSFTNGP09...
: : > Hi,
: : >
: : > I have had this problem for a long time now and I still have had no
: : > solution, I'm hoping that someone may now be able to help.
: : >
: : > The situation:
: : > Windows XP Pro SP1 - ICS Host
: : > Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
: : >
: : > Now, the following is true:
: : > 1. The Windows 2000 machine USED to connect.  Slowly, program by
: program,
: : it
: : > would stop connecting.  Now the vast majority of programs will not
: connect
: : > (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing
at
: : all
: : > has changed that would affect the network in any way.
: : > 2. A Windows 95 OSR2.1 host connects with no problems.
: : > 3. A Windows 98SE host connects with no problems.
: : > 4. Any other XP machines that are introduced to the network connect
with
: : no
: : > problems.
: : > 5. All of the clients are set up exactly the same.
: : > 6. This happened before I installed the IPv6 drivers, so IPv6 is not
: : causing
: : > the problems.
: : > 7. All machines have all available updates installed.
: : >
: : > The following is all the information I can think to give anyone who
may
: be
: : > able to help, I would zip this information but I know some newsreaders
: : dump
: : > messages with attachments.
: : >
: : >
: : > --| WINDOWS 2000 "IPCONFIG/ALL" |--
: : >
: : > Windows 2000 IP Configuration
: : >
: : >         Host Name . . . . . . . . . . . . : Win2K
: : >         Primary DNS Suffix  . . . . . . . :
: : >         Node Type . . . . . . . . . . . . : Mixed
: : >         IP Routing Enabled. . . . . . . . : No
: : >         WINS Proxy Enabled. . . . . . . . : No
: : >
: : > Ethernet adapter Home:
: : >
: : >         Connection-specific DNS Suffix  . :
: : >         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
: : NIC
: : > (3C
: : > 905-TX)
: : >         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
: : >         DHCP Enabled. . . . . . . . . . . : No
: : >         IP Address. . . . . . . . . . . . : 192.168.0.2
: : >         Subnet Mask . . . . . . . . . . . : 255.255.255.0
: : >         Default Gateway . . . . . . . . . : 192.168.0.1
: : >         DNS Servers . . . . . . . . . . . : 192.168.0.1
: : >         Primary WINS Server . . . . . . . : 192.168.0.1
: : >
: : >
: : > --| WINDOWS 2000 "NETSTAT -AN"  |--
: : >
: : > Active Connections
: : >
: : >   Proto  Local Address          Foreign Address        State
: : >   TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:1036           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:1038           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
: : >   TCP    0.0.0.0:2107  
...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by Mike » Wed, 05 Feb 2003 09:41:06


Someone previously gave incorrect information:  When using ICS, the client
must use the same gateway and DNS server and DHCP server which must use the
SAME IP address.  The ICS client must point to 192.168.0.1  for these three
settings (no other settings should have this IP address) - this is the way ICS
works.

Second, your Windows 2000 PRO ICS client looks almost right, except for the
WINS server setting.  There should be NO WINS server (WINS handles NetBIOS)
unless your XP ICS server has a real WINS server software installed - which is
not likely and would be another program, not from MS.  WINS is a name
resolution feature which is not needed if using DNS, except if your 2000 PC
has NetBIOS disabled on the NIC and you want to 'see' the 9x PC's when
browsing the network.  NetBIOS can and should still be disabled on the XP WAN
connection (dial-up/cable/dsl/whatever).

ICS is an unusual product.  It has its own built-in, stripped down version of
a DNS and a DHCP server.  Unfortunately, the DHCP server does not have an IP
exclusion list or such capability (for static addressing, like you are doing).
When using static IP addresses on ICS clients, you should manually assign IP
addresses above .128 because, by default the stripped down DHCP server sends
out 'random' IP address leases starting at lower addresses (.002-.253)
Enabling DHCP and automatic address assignment on the ICS client is best since
DHCP works with DNS on Windows 2000/XP, but it should work fine with static
settings on the client when using standard settings on the host.

I don't know how DNS works fully with ICS since it doesn't appear to do
forwarding for nslookups.  But since you have an IP6 DNS address on the XP
host, your 2000 client may be attempting to get some name resolution through
the IPv6 server since that NIC has an address listed first - essentially using
it like a translation gateway.  This may be because Windows 2000 also has IPv6
capability, but not by default.  If I were using IPv6, I would get a second
NIC and relegate it to the other NIC so that your IPv4/v6 network settings are
clean and isolated.  Otherwise, multicast/broadcast traffic is handled by the
same NIC, but because I'm not sure of the capabilities of ICS hosts (since we
know DNS/DHCP is stripped down server versions) while using multiple IP
addresses and mixed IP versions.   There are some limitations to the
capabilities to filter packets on the same NIC when using multiple IP
addresses on the same NIC.  All filters apply to all IP addresses.  Trying to
use different standards to prevent PC clients from 'seeing' another network is
not a bad idea, but you should really use multiple NIC's.  Remember, Windows
2000 clients can 'see' a lot more than 9x clients and something there is
causing the problem.

Finally, since you have an IPv6 DNS server, where is it? (It appears to be at
another IP address, separate from the three other IPv6 addresses assigned to
the NIC).   Remember, the DNS resolver on the 2000 client will append a suffix
with DNS queries and will send this to the DNS server via the same NIC - which
essentially means there is more complexity when using multiple IP versions on
the same NIC with OS'es (XP/2000) which update DNS names with appended
suffixes.  Win 9x doesn't do this.

"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:uJNp16yyCHA.2332@TK2MSFTNGP09...
> Hi,

> I have had this problem for a long time now and I still have had no
> solution, I'm hoping that someone may now be able to help.

> The situation:
> Windows XP Pro SP1 - ICS Host
> Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.

> Now, the following is true:
> 1. The Windows 2000 machine USED to connect.  Slowly, program by program, it
> would stop connecting.  Now the vast majority of programs will not connect
> (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing at all
> has changed that would affect the network in any way.
> 2. A Windows 95 OSR2.1 host connects with no problems.
> 3. A Windows 98SE host connects with no problems.
> 4. Any other XP machines that are introduced to the network connect with no
> problems.
> 5. All of the clients are set up exactly the same.
> 6. This happened before I installed the IPv6 drivers, so IPv6 is not causing
> the problems.
> 7. All machines have all available updates installed.

> The following is all the information I can think to give anyone who may be
> able to help, I would zip this information but I know some newsreaders dump
> messages with attachments.

> --| WINDOWS 2000 "IPCONFIG/ALL" |--

> Windows 2000 IP Configuration

>         Host Name . . . . . . . . . . . . : Win2K
>         Primary DNS Suffix  . . . . . . . :
>         Node Type . . . . . . . . . . . . : Mixed
>         IP Routing Enabled. . . . . . . . : No
>         WINS Proxy Enabled. . . . . . . . : No

> Ethernet adapter Home:

>         Connection-specific DNS Suffix  . :
>         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC
> (3C
> 905-TX)
>         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
>         DHCP Enabled. . . . . . . . . . . : No
>         IP Address. . . . . . . . . . . . : 192.168.0.2
>         Subnet Mask . . . . . . . . . . . : 255.255.255.0
>         Default Gateway . . . . . . . . . : 192.168.0.1
>         DNS Servers . . . . . . . . . . . : 192.168.0.1
>         Primary WINS Server . . . . . . . : 192.168.0.1

 . . .

> --|  WINDOWS 2000 "ROUTE PRINT"  |--

> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 60 08 10 45 ba ...... 3Com 3C90x Ethernet Adapter (Microsoft's
> Packet
> Scheduler)
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination        Netmask          Gateway       Interface  Metric
>           0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.2       1
>         127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
>       192.168.0.0    255.255.255.0      192.168.0.2     192.168.0.2       1
>       192.168.0.2  255.255.255.255        127.0.0.1       127.0.0.1       1
>     192.168.0.255  255.255.255.255      192.168.0.2     192.168.0.2       1
>         224.0.0.0        224.0.0.0      192.168.0.2     192.168.0.2       1
>   255.255.255.255  255.255.255.255      192.168.0.2     192.168.0.2       1
> Default Gateway:       192.168.0.1
> ===========================================================================
> Persistent Routes:
>   None

> --|  WINDOWS XP "IPCONFIG/ALL"  |--

> Windows IP Configuration

>         Host Name . . . . . . . . . . . . : WinXP
>         Primary Dns Suffix  . . . . . . . :
>         Node Type . . . . . . . . . . . . : Unknown
>         IP Routing Enabled. . . . . . . . : Yes
>         WINS Proxy Enabled. . . . . . . . : Yes

> Ethernet adapter Home:

>         Connection-specific DNS Suffix  . :
>         Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
> Ethernet
> Controller (3C905C-TX Compatible)
>         Physical Address. . . . . . . . . : 00-B0-D0-A4-5C-20
>         Dhcp Enabled. . . . . . . . . . . : No
>         IP Address. . . . . . . . . . . . : 192.168.0.1
>         Subnet Mask . . . . . . . . . . . : 255.255.255.0
>         IP Address. . . . . . . . . . . . : 2002:c0a8:1:4:1db2:6cde:23a7:1d0
>         IP Address. . . . . . . . . . . . : 2002:c0a8:1:4:2b0:d0ff:fea4:5c20
>         IP Address. . . . . . . . . . . . : fe80::2b0:d0ff:fea4:5c20%4
>         Default Gateway . . . . . . . . . :
>         DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
>                                             fec0:0:0:ffff::2%1
>                                             fec0:0:0:ffff::3%1

. . .

> --|  WINDOWS XP "ROUTE PRINT"  |--

> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 b0 d0 a4 5c 20 ...... 3Com 3C920 Integrated Fast Ethernet
> Controller (
> 3C905C-TX Compatible) - Packet Scheduler Miniport
> 0x40004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination        Netmask          Gateway       Interface  Metric
>           0.0.0.0          0.0.0.0       81.7.58.34      81.7.58.34       1
>        81.7.58.34  255.255.255.255        127.0.0.1       127.0.0.1       50
>    81.255.255.255  255.255.255.255       81.7.58.34      81.7.58.34       50
>         127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
>       192.168.0.0    255.255.255.0      192.168.0.1     192.168.0.1       20
>       192.168.0.1  255.255.255.255        127.0.0.1       127.0.0.1       20
>     192.168.0.255  255.255.255.255      192.168.0.1     192.168.0.1       20
>    213.121.147.68  255.255.255.255       81.7.58.34      81.7.58.34       1
>         224.0.0.0        240.0.0.0      192.168.0.1     192.168.0.1       20
>         224.0.0.0        240.0.0.0       81.7.58.34      81.7.58.34       1
>   255.255.255.255  255.255.255.255      192.168.0.1     192.168.0.1       1
> Default Gateway:        81.7.58.34
> ===========================================================================
> Persistent Routes:
>   None

> NOTE: The external IP changes, but it's not relevant.

> I would print the list of running processes PIDs, but I don't know how to do
> that nor if it can be done!

> Thank you to all for any help you can give.
> I'm off to cry now :'-(

> QB

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Wed, 05 Feb 2003 10:13:42


Like the title.
My responses are below.

"Mike" <mjl...@hotmail.com> wrote in message

news:C_D%9.956$2A3.20@newssvr19.news.prodigy.com...
: Someone previously gave incorrect information:  When using ICS, the client
: must use the same gateway and DNS server and DHCP server which must use
the
: SAME IP address.  The ICS client must point to 192.168.0.1  for these
three
: settings (no other settings should have this IP address) - this is the way
ICS
: works.
:
: Second, your Windows 2000 PRO ICS client looks almost right, except for
the
: WINS server setting.  There should be NO WINS server (WINS handles
NetBIOS)
: unless your XP ICS server has a real WINS server software installed -
which is
: not likely and would be another program, not from MS.  WINS is a name
: resolution feature which is not needed if using DNS, except if your 2000
PC
: has NetBIOS disabled on the NIC and you want to 'see' the 9x PC's when
: browsing the network.  NetBIOS can and should still be disabled on the XP
WAN
: connection (dial-up/cable/dsl/whatever).

The Microsoft documentation tells you to add the WINS server, I have removed
it now to see what happens.
NetBIOS is disabled on the WAN, I remember that from my very first messings
with the Internet, :-)
:
: ICS is an unusual product.  It has its own built-in, stripped down version
of
: a DNS and a DHCP server.  Unfortunately, the DHCP server does not have an
IP
: exclusion list or such capability (for static addressing, like you are
doing).
: When using static IP addresses on ICS clients, you should manually assign
IP
: addresses above .128 because, by default the stripped down DHCP server
sends
: out 'random' IP address leases starting at lower addresses (.002-.253)

Is there an error here?  You say lower addresses but you have stated .253 as
your upper limit here.  I'm just trying to not get confused at this point as
I have tried just about everything and I'm getting quite dizzy from it all.
:-(

: Enabling DHCP and automatic address assignment on the ICS client is best
since
: DHCP works with DNS on Windows 2000/XP, but it should work fine with
static
: settings on the client when using standard settings on the host.
:
: I don't know how DNS works fully with ICS since it doesn't appear to do
: forwarding for nslookups.  But since you have an IP6 DNS address on the XP
: host, your 2000 client may be attempting to get some name resolution
through
: the IPv6 server since that NIC has an address listed first - essentially
using
: it like a translation gateway.  This may be because Windows 2000 also has
IPv6
: capability, but not by default.  If I were using IPv6, I would get a
second
: NIC and relegate it to the other NIC so that your IPv4/v6 network settings
are
: clean and isolated.  Otherwise, multicast/broadcast traffic is handled by
the
: same NIC, but because I'm not sure of the capabilities of ICS hosts (since
we
: know DNS/DHCP is stripped down server versions) while using multiple IP
: addresses and mixed IP versions.   There are some limitations to the
: capabilities to filter packets on the same NIC when using multiple IP
: addresses on the same NIC.  All filters apply to all IP addresses.  Trying
to
: use different standards to prevent PC clients from 'seeing' another
network is
: not a bad idea, but you should really use multiple NIC's.  Remember,
Windows
: 2000 clients can 'see' a lot more than 9x clients and something there is
: causing the problem.

I will disable IPv6, although the problems started before it was ever
installed, to see if any difference can be noticed.

:
: Finally, since you have an IPv6 DNS server, where is it? (It appears to be
at
: another IP address, separate from the three other IPv6 addresses assigned
to
: the NIC).   Remember, the DNS resolver on the 2000 client will append a
suffix
: with DNS queries and will send this to the DNS server via the same NIC -
which
: essentially means there is more complexity when using multiple IP versions
on
: the same NIC with OS'es (XP/2000) which update DNS names with appended
: suffixes.  Win 9x doesn't do this.

The XP ICS server is all of those IPv6 addresses, below is "IPV6 IF" to try
and explain:

Interface 4: Ethernet: LAN
{6CCC3212-F897-4CCA-B217-CDE97E4E16AE}
  zones: link 4 site 2
  uses Neighbor Discovery
  uses Router Discovery
  sends Router Advertisements
  forwards packets
  link-layer address: 00-b0-d0-a4-5c-20
    preferred global 2002:c0a8:1:4:a8e6:5ae6:9e3c:9b18, life
47h57m25s/27m25s (a
nonymous)
    preferred global 2002:c0a8:1:4:2b0:d0ff:fea4:5c20, life 47h57m25s/27m25s
(pu
blic)
    preferred site-local fec0::4:2b0:d0ff:fea4:5c20, life 47h57m25s/27m25s
(publ
ic)
    preferred link-local fe80::2b0:d0ff:fea4:5c20, life infinite
    multicast interface-local ff01::1, 1 refs, not reportable
    multicast link-local ff02::1, 1 refs, not reportable
    multicast link-local ff02::1:ffa4:5c20, 3 refs, last reporter
    multicast interface-local ff01::2, 1 refs, not reportable
    multicast link-local ff02::2, 1 refs, last reporter
    multicast site-local ff05::2, 1 refs, last reporter
    anycast site-local fec0:0:0:4::
    multicast link-local ff02::1:ff00:0, 2 refs, last reporter
    multicast link-local ff02::1:ff3c:9b18, 1 refs, last reporter
    anycast global 2002:c0a8:1:4::
  link MTU 1496 (true link MTU 1496)
  current hop limit 128
  reachable time 24000ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 1
Interface 3: 6to4 Tunneling Pseudo-Interface
{A995346E-9F3E-2EDB-47D1-9CC7BA01CD73}
  does not use Neighbor Discovery
  does not use Router Discovery
  forwards packets
  routing preference 1
    preferred global 2002:5107:37cf::5107:37cf, life infinite
  link MTU 1280 (true link MTU 65515)
  current hop limit 128
  reachable time 27500ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 0
Interface 2: Automatic Tunneling Pseudo-Interface
{48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}
  does not use Neighbor Discovery
  does not use Router Discovery
  forwards packets
  routing preference 1
  EUI-64 embedded IPv4 address: 0.0.0.0
  router link-layer address: 0.0.0.0
    preferred link-local fe80::5efe:81.7.55.207, life infinite
    preferred link-local fe80::5efe:192.168.0.1, life infinite
  link MTU 1280 (true link MTU 65515)
  current hop limit 128
  reachable time 35500ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 0
Interface 1: Loopback Pseudo-Interface
{6BD113CC-5EC2-7638-B953-0B889DA72014}
  does not use Neighbor Discovery
  does not use Router Discovery
  link-layer address:
    preferred link-local ::1, life infinite
    preferred link-local fe80::1, life infinite
  link MTU 1500 (true link MTU 4294967295)
  current hop limit 128
  reachable time 41000ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 0

The RFC for IPv6 states that it is likely that a machine has multiple IPv6
addresses, it seems to function OK so I just leave it.
Not that I can manually configure it anyway!

Thank you for the information :-D
I will make some adjustments and see if anything helps.
Thanks again,
QB

:
:
:

: "QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

: news:uJNp16yyCHA.2332@TK2MSFTNGP09...
: > Hi,
: >
: > I have had this problem for a long time now and I still have had no
: > solution, I'm hoping that someone may now be able to help.
: >
: > The situation:
: > Windows XP Pro SP1 - ICS Host
: > Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
: >
: > Now, the following is true:
: > 1. The Windows 2000 machine USED to connect.  Slowly, program by
program, it
: > would stop connecting.  Now the vast majority of programs will not
connect
: > (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing at
all
: > has changed that would affect the network in any way.
: > 2. A Windows 95 OSR2.1 host connects with no problems.
: > 3. A Windows 98SE host connects with no problems.
: > 4. Any other XP machines that are introduced to the network connect with
no
: > problems.
: > 5. All of the clients are set up exactly the same.
: > 6. This happened before I installed the IPv6 drivers, so IPv6 is not
causing
: > the problems.
: > 7. All machines have all available updates installed.
: >
: > The following is all the information I can think to give anyone who may
be
: > able to help, I would zip this information but I know some newsreaders
dump
: > messages with attachments.
: >
: >
: > --| WINDOWS 2000 "IPCONFIG/ALL" |--
: >
: > Windows 2000 IP Configuration
: >
: >         Host Name . . . . . . . . . . . . : Win2K
: >         Primary DNS Suffix  . . . . . . . :
: >         Node Type . . . . . . . . . . . . : Mixed
: >         IP Routing Enabled. . . . . . . . : No
: >         WINS Proxy Enabled. . . . . . . . : No
: >
: > Ethernet adapter Home:
: >
: >         Connection-specific DNS Suffix  . :
: >         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
NIC
: > (3C
: > 905-TX)
: >         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
: >         DHCP Enabled. . . . . . . . . . . : No
: >         IP Address. . . . . . . . . . . . : 192.168.0.2
: >         Subnet Mask . . . . . . . . . . . : 255.255.255.0
: >         Default Gateway . . . . . . . . . : 192.168.0.1
: >         DNS Servers . . . . . . . . . . . : 192.168.0.1
: >         Primary WINS Server . . . . . . . : 192.168.0.1
: >
:  . . .
: >
: >
: > --|  WINDOWS 2000 "ROUTE PRINT"  |--
: >
: >
===========================================================================
: > Interface List
: > 0x1 ........................... MS TCP Loopback interface
: > 0x2 ...00 60 08 10 45 ba ...... 3Com 3C90x Ethernet Adapter (Microsoft's
: > Packet
: > Scheduler)
: >
===========================================================================
: >
===========================================================================
: > Active Routes:
: > Network Destination        Netmask          Gateway       Interface
Metric
: >          
...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Fri, 07 Feb 2003 08:13:12


Changing these settings did not affect anything.  My system is now the way
it was before (and the way it was when ICS was working).

So if anyone has any other suggestions I'm extremely willing to try.
Only sensible suggestions though please.

Thanks.

"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:#vmbXq#yCHA.640@TK2MSFTNGP12...
: Like the title.
: My responses are below.
:
:
: "Mike" <mjl...@hotmail.com> wrote in message

: news:C_D%9.956$2A3.20@newssvr19.news.prodigy.com...
: : Someone previously gave incorrect information:  When using ICS, the
client
: : must use the same gateway and DNS server and DHCP server which must use
: the
: : SAME IP address.  The ICS client must point to 192.168.0.1  for these
: three
: : settings (no other settings should have this IP address) - this is the
way
: ICS
: : works.
: :
: : Second, your Windows 2000 PRO ICS client looks almost right, except for
: the
: : WINS server setting.  There should be NO WINS server (WINS handles
: NetBIOS)
: : unless your XP ICS server has a real WINS server software installed -
: which is
: : not likely and would be another program, not from MS.  WINS is a name
: : resolution feature which is not needed if using DNS, except if your 2000
: PC
: : has NetBIOS disabled on the NIC and you want to 'see' the 9x PC's when
: : browsing the network.  NetBIOS can and should still be disabled on the
XP
: WAN
: : connection (dial-up/cable/dsl/whatever).
:
: The Microsoft documentation tells you to add the WINS server, I have
removed
: it now to see what happens.
: NetBIOS is disabled on the WAN, I remember that from my very first
messings
: with the Internet, :-)
: :
: : ICS is an unusual product.  It has its own built-in, stripped down
version
: of
: : a DNS and a DHCP server.  Unfortunately, the DHCP server does not have
an
: IP
: : exclusion list or such capability (for static addressing, like you are
: doing).
: : When using static IP addresses on ICS clients, you should manually assig
n
: IP
: : addresses above .128 because, by default the stripped down DHCP server
: sends
: : out 'random' IP address leases starting at lower addresses (.002-.253)
:
: Is there an error here?  You say lower addresses but you have stated .253
as
: your upper limit here.  I'm just trying to not get confused at this point
as
: I have tried just about everything and I'm getting quite dizzy from it
all.
: :-(
:
: : Enabling DHCP and automatic address assignment on the ICS client is best
: since
: : DHCP works with DNS on Windows 2000/XP, but it should work fine with
: static
: : settings on the client when using standard settings on the host.
: :
: : I don't know how DNS works fully with ICS since it doesn't appear to do
: : forwarding for nslookups.  But since you have an IP6 DNS address on the
XP
: : host, your 2000 client may be attempting to get some name resolution
: through
: : the IPv6 server since that NIC has an address listed first - essentially
: using
: : it like a translation gateway.  This may be because Windows 2000 also
has
: IPv6
: : capability, but not by default.  If I were using IPv6, I would get a
: second
: : NIC and relegate it to the other NIC so that your IPv4/v6 network
settings
: are
: : clean and isolated.  Otherwise, multicast/broadcast traffic is handled
by
: the
: : same NIC, but because I'm not sure of the capabilities of ICS hosts
(since
: we
: : know DNS/DHCP is stripped down server versions) while using multiple IP
: : addresses and mixed IP versions.   There are some limitations to the
: : capabilities to filter packets on the same NIC when using multiple IP
: : addresses on the same NIC.  All filters apply to all IP addresses.
Trying
: to
: : use different standards to prevent PC clients from 'seeing' another
: network is
: : not a bad idea, but you should really use multiple NIC's.  Remember,
: Windows
: : 2000 clients can 'see' a lot more than 9x clients and something there is
: : causing the problem.
:
: I will disable IPv6, although the problems started before it was ever
: installed, to see if any difference can be noticed.
:
: :
: : Finally, since you have an IPv6 DNS server, where is it? (It appears to
be
: at
: : another IP address, separate from the three other IPv6 addresses
assigned
: to
: : the NIC).   Remember, the DNS resolver on the 2000 client will append a
: suffix
: : with DNS queries and will send this to the DNS server via the same NIC -
: which
: : essentially means there is more complexity when using multiple IP
versions
: on
: : the same NIC with OS'es (XP/2000) which update DNS names with appended
: : suffixes.  Win 9x doesn't do this.
:
: The XP ICS server is all of those IPv6 addresses, below is "IPV6 IF" to
try
: and explain:
:
: Interface 4: Ethernet: LAN
: {6CCC3212-F897-4CCA-B217-CDE97E4E16AE}
:   zones: link 4 site 2
:   uses Neighbor Discovery
:   uses Router Discovery
:   sends Router Advertisements
:   forwards packets
:   link-layer address: 00-b0-d0-a4-5c-20
:     preferred global 2002:c0a8:1:4:a8e6:5ae6:9e3c:9b18, life
: 47h57m25s/27m25s (a
: nonymous)
:     preferred global 2002:c0a8:1:4:2b0:d0ff:fea4:5c20, life
47h57m25s/27m25s
: (pu
: blic)
:     preferred site-local fec0::4:2b0:d0ff:fea4:5c20, life 47h57m25s/27m25s
: (publ
: ic)
:     preferred link-local fe80::2b0:d0ff:fea4:5c20, life infinite
:     multicast interface-local ff01::1, 1 refs, not reportable
:     multicast link-local ff02::1, 1 refs, not reportable
:     multicast link-local ff02::1:ffa4:5c20, 3 refs, last reporter
:     multicast interface-local ff01::2, 1 refs, not reportable
:     multicast link-local ff02::2, 1 refs, last reporter
:     multicast site-local ff05::2, 1 refs, last reporter
:     anycast site-local fec0:0:0:4::
:     multicast link-local ff02::1:ff00:0, 2 refs, last reporter
:     multicast link-local ff02::1:ff3c:9b18, 1 refs, last reporter
:     anycast global 2002:c0a8:1:4::
:   link MTU 1496 (true link MTU 1496)
:   current hop limit 128
:   reachable time 24000ms (base 30000ms)
:   retransmission interval 1000ms
:   DAD transmits 1
: Interface 3: 6to4 Tunneling Pseudo-Interface
: {A995346E-9F3E-2EDB-47D1-9CC7BA01CD73}
:   does not use Neighbor Discovery
:   does not use Router Discovery
:   forwards packets
:   routing preference 1
:     preferred global 2002:5107:37cf::5107:37cf, life infinite
:   link MTU 1280 (true link MTU 65515)
:   current hop limit 128
:   reachable time 27500ms (base 30000ms)
:   retransmission interval 1000ms
:   DAD transmits 0
: Interface 2: Automatic Tunneling Pseudo-Interface
: {48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}
:   does not use Neighbor Discovery
:   does not use Router Discovery
:   forwards packets
:   routing preference 1
:   EUI-64 embedded IPv4 address: 0.0.0.0
:   router link-layer address: 0.0.0.0
:     preferred link-local fe80::5efe:81.7.55.207, life infinite
:     preferred link-local fe80::5efe:192.168.0.1, life infinite
:   link MTU 1280 (true link MTU 65515)
:   current hop limit 128
:   reachable time 35500ms (base 30000ms)
:   retransmission interval 1000ms
:   DAD transmits 0
: Interface 1: Loopback Pseudo-Interface
: {6BD113CC-5EC2-7638-B953-0B889DA72014}
:   does not use Neighbor Discovery
:   does not use Router Discovery
:   link-layer address:
:     preferred link-local ::1, life infinite
:     preferred link-local fe80::1, life infinite
:   link MTU 1500 (true link MTU 4294967295)
:   current hop limit 128
:   reachable time 41000ms (base 30000ms)
:   retransmission interval 1000ms
:   DAD transmits 0
:
:
: The RFC for IPv6 states that it is likely that a machine has multiple IPv6
: addresses, it seems to function OK so I just leave it.
: Not that I can manually configure it anyway!
:
:
: Thank you for the information :-D
: I will make some adjustments and see if anything helps.
: Thanks again,
: QB
:
: :
: :
: :
: : "QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message
: : news:uJNp16yyCHA.2332@TK2MSFTNGP09...
: : > Hi,
: : >
: : > I have had this problem for a long time now and I still have had no
: : > solution, I'm hoping that someone may now be able to help.
: : >
: : > The situation:
: : > Windows XP Pro SP1 - ICS Host
: : > Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
: : >
: : > Now, the following is true:
: : > 1. The Windows 2000 machine USED to connect.  Slowly, program by
: program, it
: : > would stop connecting.  Now the vast majority of programs will not
: connect
: : > (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing
at
: all
: : > has changed that would affect the network in any way.
: : > 2. A Windows 95 OSR2.1 host connects with no problems.
: : > 3. A Windows 98SE host connects with no problems.
: : > 4. Any other XP machines that are introduced to the network connect
with
: no
: : > problems.
: : > 5. All of the clients are set up exactly the same.
: : > 6. This happened before I installed the IPv6 drivers, so IPv6 is not
: causing
: : > the problems.
: : > 7. All machines have all available updates installed.
: : >
: : > The following is all the information I can think to give anyone who
may
: be
: : > able to help, I would zip this information but I know some newsreaders
: dump
: : > messages with attachments.
: : >
: : >
: : > --| WINDOWS 2000 "IPCONFIG/ALL" |--
: : >
: : > Windows 2000 IP Configuration
: : >
: : >         Host Name . . . . . . . . . . . . : Win2K
: : >         Primary DNS Suffix  . . . . . . . :
: : >         Node Type . . . . . . . . . . . . : Mixed
: : >         IP Routing Enabled. . . . . . . . : No
: : >         WINS Proxy Enabled. . . . . . . . : No
: : >
: : > Ethernet adapter Home:
: : >
: : >         Connection-specific DNS Suffix  . :
: : >         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
: NIC
: : > (3C
: : > 905-TX)
: : >         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
: : >         DHCP Enabled. . . . . . . . . . . : No
: : >         IP Address. . . . . . . . . . . . : 192.168.0.2
: : >      
...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Sat, 08 Feb 2003 10:37:12


I know I'm not the only one with this problem, why doesn't anyone have a
solution??

"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:uJNp16yyCHA.2332@TK2MSFTNGP09...
: Hi,
:
: I have had this problem for a long time now and I still have had no
: solution, I'm hoping that someone may now be able to help.
:
: The situation:
: Windows XP Pro SP1 - ICS Host
: Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
:
: Now, the following is true:
: 1. The Windows 2000 machine USED to connect.  Slowly, program by program,
it
: would stop connecting.  Now the vast majority of programs will not connect
: (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing at
all
: has changed that would affect the network in any way.
: 2. A Windows 95 OSR2.1 host connects with no problems.
: 3. A Windows 98SE host connects with no problems.
: 4. Any other XP machines that are introduced to the network connect with
no
: problems.
: 5. All of the clients are set up exactly the same.
: 6. This happened before I installed the IPv6 drivers, so IPv6 is not
causing
: the problems.
: 7. All machines have all available updates installed.
:
: The following is all the information I can think to give anyone who may be
: able to help, I would zip this information but I know some newsreaders
dump
: messages with attachments.
:
:
: --| WINDOWS 2000 "IPCONFIG/ALL" |--
:
: Windows 2000 IP Configuration
:
:         Host Name . . . . . . . . . . . . : Win2K
:         Primary DNS Suffix  . . . . . . . :
:         Node Type . . . . . . . . . . . . : Mixed
:         IP Routing Enabled. . . . . . . . : No
:         WINS Proxy Enabled. . . . . . . . : No
:
: Ethernet adapter Home:
:
:         Connection-specific DNS Suffix  . :
:         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
NIC
: (3C
: 905-TX)
:         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
:         DHCP Enabled. . . . . . . . . . . : No
:         IP Address. . . . . . . . . . . . : 192.168.0.2
:         Subnet Mask . . . . . . . . . . . : 255.255.255.0
:         Default Gateway . . . . . . . . . : 192.168.0.1
:         DNS Servers . . . . . . . . . . . : 192.168.0.1
:         Primary WINS Server . . . . . . . : 192.168.0.1
:
:
: --| WINDOWS 2000 "NETSTAT -AN"  |--
:
: Active Connections
:
:   Proto  Local Address          Foreign Address        State
:   TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1036           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1038           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2774           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2792           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:3372           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING
:   TCP    127.0.0.1:6555         0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:23         192.168.0.1:3093       ESTABLISHED
:   TCP    192.168.0.2:139        0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:139        192.168.0.1:3021       ESTABLISHED
:   TCP    192.168.0.2:2774       192.168.0.1:1504       ESTABLISHED
:   TCP    192.168.0.2:2775       0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:2784       0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:2784       192.168.0.1:139        ESTABLISHED
:   TCP    192.168.0.2:2792       192.168.0.1:1999       ESTABLISHED
:   UDP    0.0.0.0:7              *:*
:   UDP    0.0.0.0:9              *:*
:   UDP    0.0.0.0:13             *:*
:   UDP    0.0.0.0:17             *:*
:   UDP    0.0.0.0:19             *:*
:   UDP    0.0.0.0:135            *:*
:   UDP    0.0.0.0:161            *:*
:   UDP    0.0.0.0:445            *:*
:   UDP    0.0.0.0:1037           *:*
:   UDP    0.0.0.0:1040           *:*
:   UDP    0.0.0.0:3456           *:*
:   UDP    0.0.0.0:3527           *:*
:   UDP    0.0.0.0:38037          *:*
:   UDP    192.168.0.2:137        *:*
:   UDP    192.168.0.2:138        *:*
:   UDP    192.168.0.2:500        *:*
:   UDP    192.168.0.2:520        *:*
:
:
:
: --|  WINDOWS 2000 "ROUTE PRINT"  |--
:
:
===========================================================================
: Interface List
: 0x1 ........................... MS TCP Loopback interface
: 0x2 ...00 60 08 10 45 ba ...... 3Com 3C90x Ethernet Adapter (Microsoft's
: Packet
: Scheduler)
:
===========================================================================
:
===========================================================================
: Active Routes:
: Network Destination        Netmask          Gateway       Interface
Metric
:           0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.2
1
:         127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1
1
:       192.168.0.0    255.255.255.0      192.168.0.2     192.168.0.2
1
:       192.168.0.2  255.255.255.255        127.0.0.1       127.0.0.1
1
:     192.168.0.255  255.255.255.255      192.168.0.2     192.168.0.2
1
:         224.0.0.0        224.0.0.0      192.168.0.2     192.168.0.2
1
:   255.255.255.255  255.255.255.255      192.168.0.2     192.168.0.2
1
: Default Gateway:       192.168.0.1
:
===========================================================================
: Persistent Routes:
:   None
:
:
: --|  WINDOWS XP "IPCONFIG/ALL"  |--
:
: Windows IP Configuration
:
:         Host Name . . . . . . . . . . . . : WinXP
:         Primary Dns Suffix  . . . . . . . :
:         Node Type . . . . . . . . . . . . : Unknown
:         IP Routing Enabled. . . . . . . . : Yes
:         WINS Proxy Enabled. . . . . . . . : Yes
:
: Ethernet adapter Home:
:
:         Connection-specific DNS Suffix  . :
:         Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
: Ethernet
: Controller (3C905C-TX Compatible)
:         Physical Address. . . . . . . . . : 00-B0-D0-A4-5C-20
:         Dhcp Enabled. . . . . . . . . . . : No
:         IP Address. . . . . . . . . . . . : 192.168.0.1
:         Subnet Mask . . . . . . . . . . . : 255.255.255.0
:         IP Address. . . . . . . . . . . . :
2002:c0a8:1:4:1db2:6cde:23a7:1d0
:         IP Address. . . . . . . . . . . . :
2002:c0a8:1:4:2b0:d0ff:fea4:5c20
:         IP Address. . . . . . . . . . . . : fe80::2b0:d0ff:fea4:5c20%4
:         Default Gateway . . . . . . . . . :
:         DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
:                                             fec0:0:0:ffff::2%1
:                                             fec0:0:0:ffff::3%1
:
:
: --|  WINDOWS XP "NETSTAT -AON"  |--
:
: Active Connections
:
:   Proto  Local Address          Foreign Address        State           PID
:   TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING       300
:   TCP    0.0.0.0:59             0.0.0.0:0              LISTENING       760
:   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       860
:   TCP    0.0.0.0:251            0.0.0.0:0              LISTENING       968
:   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
:   TCP    0.0.0.0:1024           0.0.0.0:0              LISTENING
3492
:   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       968
:   TCP    0.0.0.0:1027           0.0.0.0:0              LISTENING
1536
:   TCP    0.0.0.0:1030           0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:1033           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:1034           0.0.0.0:0              LISTENING       4
:   TCP    0.0.0.0:1080           0.0.0.0:0              LISTENING
1936
:   TCP    0.0.0.0:1504           0.0.0.0:0              LISTENING       224
:   TCP    0.0.0.0:1505           0.0.0.0:0              LISTENING       224
:   TCP    0.0.0.0:1506           0.0.0.0:0              LISTENING       224
:   TCP    0.0.0.0:1723           0.0.0.0:0              LISTENING       4
:   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:1999           0.0.0.0:0              LISTENING       396
:   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
1196
:   TCP    0.0.0.0:3023           0.0.0.0:0              LISTENING
1196
:   TCP    0.0.0.0:3026           0.0.0.0:0              LISTENING
1744
:   TCP    0.0.0.0:3033           0.0.0.0:0              LISTENING
1196
:   TCP    0.0.0.0:3034           0.0.0.0:0              LISTENING
4048
:   TCP  
...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Thu, 20 Feb 2003 01:49:41


?
"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:e0lAXV#yCHA.1580@TK2MSFTNGP09...
: The DNS proxy agent was unable to read the local list of name-resolution
: servers from the registry. The data is the error code.
:
: From the Event Log, will this have anything to do with it?
:
:
:
: "QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

: news:ezeOpw4yCHA.1900@TK2MSFTNGP10...
: : Sure can :)
: :
: : --|  WIN 2000 "PATHPING YAHOO.COM"  |--
: :
: :
: :
: : Tracing route to yahoo.com [64.58.79.230]
: :
: : over a maximum of 30 hops:
: :
: :   0  win2k [192.168.0.2]
: :
: :   1  WinXP.mshome.net [192.168.0.1]
: :
: :   2  vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]
: :
: :   3  192.168.253.2
: :
: :   4  172.16.56.177
: :
: :   5  172.16.50.133
: :
: :   6  172.16.50.7
: :
: :   7  213.121.156.21
: :
: :   8  core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]
: :
: :   9  core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]
: :
: :  10  core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]
: :
: :  11  core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]
: :
: :  12  transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]
: :
: :  13  transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]
: :
: :  14  exchange-cust1.ash.equinix.net [206.223.115.16]
: :
: :  15  ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]
: :
: :  16  vl43.bas1.dcx.yahoo.com [216.109.120.190]
: :
: :  17
: :
: : Computing statistics for 425 seconds...
: :
: :             Source to Here   This Node/Link
: :
: : Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
: :
: :   0                                           win2k [192.168.0.2]
: :
: :                                 0/ 100 =  0%   |
: :
: :   1    0ms     0/ 100 =  0%     0/ 100 =  0%  WinXP.mshome.net
: [192.168.0.1]
: :
: :                               100/ 100 =100%   |
: :
: :   2  ---     100/ 100 =100%     0/ 100 =  0%
: : vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net [213.121.147.68]
: :
: :                                 0/ 100 =  0%   |
: :
: :   3  ---     100/ 100 =100%     0/ 100 =  0%  192.168.253.2
: :
: :                                 0/ 100 =  0%   |
: :
: :   4  ---     100/ 100 =100%     0/ 100 =  0%  172.16.56.177
: :
: :                                 0/ 100 =  0%   |
: :
: :   5  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.133
: :
: :                                 0/ 100 =  0%   |
: :
: :   6  ---     100/ 100 =100%     0/ 100 =  0%  172.16.50.7
: :
: :                                 0/ 100 =  0%   |
: :
: :   7  ---     100/ 100 =100%     0/ 100 =  0%  213.121.156.21
: :
: :                                 0/ 100 =  0%   |
: :
: :   8  ---     100/ 100 =100%     0/ 100 =  0%
: : core1-gig2-0.rochdale.ukcore.bt.net [217.32.168.1]
: :
: :                                 0/ 100 =  0%   |
: :
: :   9  ---     100/ 100 =100%     0/ 100 =  0%
: : core1-pos5-1.birmingham.ukcore.bt.net [194.74.16.189]
: :
: :                                 0/ 100 =  0%   |
: :
: :  10  ---     100/ 100 =100%     0/ 100 =  0%
: : core1-pos13-2.reading.ukcore.bt.net [62.6.196.106]
: :
: :                                 0/ 100 =  0%   |
: :
: :  11  ---     100/ 100 =100%     0/ 100 =  0%
: : core1-pos5-1.ealing.ukcore.bt.net [195.99.120.205]
: :
: :                                 0/ 100 =  0%   |
: :
: :  12  ---     100/ 100 =100%     0/ 100 =  0%
: : transit1-pos3-0.ealing.ukcore.bt.net [194.72.9.234]
: :
: :                                 0/ 100 =  0%   |
: :
: :  13  ---     100/ 100 =100%     0/ 100 =  0%
: : transit2-pos8-0.washington.ukcore.bt.net [194.72.9.14]
: :
: :                                 0/ 100 =  0%   |
: :
: :  14  ---     100/ 100 =100%     0/ 100 =  0%
: exchange-cust1.ash.equinix.net
: : [206.223.115.16]
: :
: :                                 0/ 100 =  0%   |
: :
: :  15  ---     100/ 100 =100%     0/ 100 =  0%
: : ge-0-3-0-p34.msr1.dcn.yahoo.com [216.109.120.161]
: :
: :                                 0/ 100 =  0%   |
: :
: :  16  ---     100/ 100 =100%     0/ 100 =  0%  vl43.bas1.dcx.yahoo.com
: : [216.109.120.190]
: :
: :                                 0/ 100 =  0%   |
: :
: :  17  ---     100/ 100 =100%     0/ 100 =  0%  Ken [0.0.0.0]
: :
: :
: :
: : Trace complete.
: :
: : ...
: :
: :
: : --|  WIN 2000 "TRACERT YAHOO.COM"  |--
: :
: : Tracing route to yahoo.com [64.58.79.230]
: : over a maximum of 30 hops:
: :
: :   1   <10 ms   <10 ms   <10 ms  WinXP.mshome.net [192.168.0.1]
: :   2   180 ms   200 ms   191 ms
vsn0177846-v21-co-uk-ltd-fer-1.mdip.bt.net
: : [213.
: : 121.147.68]
: :   3   180 ms   191 ms   190 ms  192.168.253.2
: :   4   170 ms   191 ms   180 ms  172.16.56.177
: :   5   180 ms   180 ms   181 ms  172.16.50.133
: :   6   180 ms   240 ms   190 ms  172.16.50.8
: :   7   161 ms   180 ms   180 ms  213.121.156.25
: :   8   170 ms   181 ms   170 ms  core2-gig3-0.rochdale.ukcore.bt.net
: : [217.32.168.
: : 66]
: :   9   171 ms   170 ms   170 ms  core2-pos5-1.birmingham.ukcore.bt.net
: : [194.74.16
: : .193]
: :  10   170 ms   160 ms   170 ms  core2-pos13-2.reading.ukcore.bt.net
: : [62.6.196.11
: : 0]
: :  11   180 ms   190 ms   171 ms  core2-pos13-1.ealing.ukcore.bt.net
: : [62.6.196.242
: : ]
: :  12   170 ms   181 ms   190 ms  transit1-pos4-0.ealing.ukcore.bt.net
: : [194.72.9.2
: : 38]
: :  13   250 ms   250 ms   251 ms  transit2-pos8-0.washington.ukcore.bt.net
: : [194.72
: : .9.14]
: :  14   270 ms   261 ms   270 ms  exchange-cust1.ash.equinix.net
: : [206.223.115.16]
: :
: :  15   261 ms   270 ms   260 ms  ge-0-3-0-p34.msr1.dcn.yahoo.com
: : [216.109.120.161
: : ]
: :  16     *      281 ms     *     vl43.bas1.dcx.yahoo.com
[216.109.120.190]
: :  17     *        *        *     Request timed out.
: :  18     *        *        *     Request timed out.
: :  19     *        *        *     Request timed out.
: :  20     *        *        *     Request timed out.
: :  21     *        *     ^C
: :
: :
: :
: : I never asked for the ".mshome.net" but I don't know how to get rid of
it.
: : :-(
: :
: : Cheers.
: :
: :
: : "Robert L" <bobli...@hotmail.com> wrote in message
: : news:eTXWoizyCHA.2232@TK2MSFTNGP11...
: : : could you also please post pathping yahoo.com from w2k?
: : :
: : : --
: : : For more information, go to  http://www25.brinkster.com/ChicagoTech
: : :
: : : Please don't send e-mail or reply to me except you need consulting
: : services.
: : : Posting on MS newsgroup will benefit all readers and you may get more
: : help.
: : :
: : : Robert Lin, CNE & MCSE
: : : Windows & Network Support, Tips and FAQs on
: : : http://www25.brinkster.com/ChicagoTech
: : : This posting is provided "AS IS" with no warranties.
: : :
: : : "QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message
: : : news:uJNp16yyCHA.2332@TK2MSFTNGP09...
: : : > Hi,
: : : >
: : : > I have had this problem for a long time now and I still have had no
: : : > solution, I'm hoping that someone may now be able to help.
: : : >
: : : > The situation:
: : : > Windows XP Pro SP1 - ICS Host
: : : > Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
: : : >
: : : > Now, the following is true:
: : : > 1. The Windows 2000 machine USED to connect.  Slowly, program by
: : program,
: : : it
: : : > would stop connecting.  Now the vast majority of programs will not
: : connect
: : : > (including all the Microsoft apps - strangely, WinAmp DOES).
Nothing
: at
: : : all
: : : > has changed that would affect the network in any way.
: : : > 2. A Windows 95 OSR2.1 host connects with no problems.
: : : > 3. A Windows 98SE host connects with no problems.
: : : > 4. Any other XP machines that are introduced to the network connect
: with
: : : no
: : : > problems.
: : : > 5. All of the clients are set up exactly the same.
: : : > 6. This happened before I installed the IPv6 drivers, so IPv6 is not
: : : causing
: : : > the problems.
: : : > 7. All machines have all available updates installed.
: : : >
: : : > The following is all the information I can think to give anyone who
: may
: : be
: : : > able to help, I would zip this information but I know some
newsreaders
: : : dump
: : : > messages with attachments.
: : : >
: : : >
: : : > --| WINDOWS 2000 "IPCONFIG/ALL" |--
: : : >
: : : > Windows 2000 IP Configuration
: : : >
: : : >         Host Name . . . . . . . . . . . . : Win2K
: : : >         Primary DNS Suffix  . . . . . . . :
: : : >         Node Type . . . . . . . . . . . . : Mixed
: : : >         IP Routing Enabled. . . . . . . . : No
: : : >         WINS Proxy Enabled. . . . . . . . : No
: : : >
: : : > Ethernet adapter Home:
: : : >
: : : >         Connection-specific DNS Suffix  . :
: : : >         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
: PCI
: : : NIC
: : : > (3C
: : : > 905-TX)
: : : >         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
: : : >         DHCP Enabled. . . . . . . . . . . : No
: : : >         IP Address. . . . . . . . . . . . : 192.168.0.2
: : : >         Subnet Mask . . . . . . . . . . . : 255.255.255.0
: : : >         Default Gateway . . . . . . . . . : 192.168.0.1
: : : >         DNS Servers . . . . . . . . . . . : 192.168.0.1
: : : >         Primary WINS Server . . . . . . . : 192.168.0.1
: : : >
: : : >
: : : > --| WINDOWS 2000 "NETSTAT -AN"  |--
: : : >
: : : > Active Connections
: : : >
: : : >   Proto  Local Address          Foreign Address        State
: : : >   TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
: : : >   TCP    0.0.0.0:443          
...

read more »

 
 
 

Win 2000 Pro Client ---> Win XP Pro ICS Host won't route.

Post by QuarkBom » Thu, 20 Feb 2003 01:50:12


Surely there is someone out there that has some idea! :-(

"QuarkBomb" <MyMonkeyHu...@InYourButt.com> wrote in message

news:uJNp16yyCHA.2332@TK2MSFTNGP09...
: Hi,
:
: I have had this problem for a long time now and I still have had no
: solution, I'm hoping that someone may now be able to help.
:
: The situation:
: Windows XP Pro SP1 - ICS Host
: Windows 2000 Pro SP3 - ICS Client  = Won't connect to the Internet.
:
: Now, the following is true:
: 1. The Windows 2000 machine USED to connect.  Slowly, program by program,
it
: would stop connecting.  Now the vast majority of programs will not connect
: (including all the Microsoft apps - strangely, WinAmp DOES).  Nothing at
all
: has changed that would affect the network in any way.
: 2. A Windows 95 OSR2.1 host connects with no problems.
: 3. A Windows 98SE host connects with no problems.
: 4. Any other XP machines that are introduced to the network connect with
no
: problems.
: 5. All of the clients are set up exactly the same.
: 6. This happened before I installed the IPv6 drivers, so IPv6 is not
causing
: the problems.
: 7. All machines have all available updates installed.
:
: The following is all the information I can think to give anyone who may be
: able to help, I would zip this information but I know some newsreaders
dump
: messages with attachments.
:
:
: --| WINDOWS 2000 "IPCONFIG/ALL" |--
:
: Windows 2000 IP Configuration
:
:         Host Name . . . . . . . . . . . . : Win2K
:         Primary DNS Suffix  . . . . . . . :
:         Node Type . . . . . . . . . . . . : Mixed
:         IP Routing Enabled. . . . . . . . : No
:         WINS Proxy Enabled. . . . . . . . : No
:
: Ethernet adapter Home:
:
:         Connection-specific DNS Suffix  . :
:         Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
NIC
: (3C
: 905-TX)
:         Physical Address. . . . . . . . . : 00-60-08-10-45-BA
:         DHCP Enabled. . . . . . . . . . . : No
:         IP Address. . . . . . . . . . . . : 192.168.0.2
:         Subnet Mask . . . . . . . . . . . : 255.255.255.0
:         Default Gateway . . . . . . . . . : 192.168.0.1
:         DNS Servers . . . . . . . . . . . : 192.168.0.1
:         Primary WINS Server . . . . . . . : 192.168.0.1
:
:
: --| WINDOWS 2000 "NETSTAT -AN"  |--
:
: Active Connections
:
:   Proto  Local Address          Foreign Address        State
:   TCP    0.0.0.0:7              0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:9              0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:13             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:17             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:19             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1036           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1038           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2774           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:2792           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:3372           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING
:   TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING
:   TCP    127.0.0.1:6555         0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:23         192.168.0.1:3093       ESTABLISHED
:   TCP    192.168.0.2:139        0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:139        192.168.0.1:3021       ESTABLISHED
:   TCP    192.168.0.2:2774       192.168.0.1:1504       ESTABLISHED
:   TCP    192.168.0.2:2775       0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:2784       0.0.0.0:0              LISTENING
:   TCP    192.168.0.2:2784       192.168.0.1:139        ESTABLISHED
:   TCP    192.168.0.2:2792       192.168.0.1:1999       ESTABLISHED
:   UDP    0.0.0.0:7              *:*
:   UDP    0.0.0.0:9              *:*
:   UDP    0.0.0.0:13             *:*
:   UDP    0.0.0.0:17             *:*
:   UDP    0.0.0.0:19             *:*
:   UDP    0.0.0.0:135            *:*
:   UDP    0.0.0.0:161            *:*
:   UDP    0.0.0.0:445            *:*
:   UDP    0.0.0.0:1037           *:*
:   UDP    0.0.0.0:1040           *:*
:   UDP    0.0.0.0:3456           *:*
:   UDP    0.0.0.0:3527           *:*
:   UDP    0.0.0.0:38037          *:*
:   UDP    192.168.0.2:137        *:*
:   UDP    192.168.0.2:138        *:*
:   UDP    192.168.0.2:500        *:*
:   UDP    192.168.0.2:520        *:*
:
:
:
: --|  WINDOWS 2000 "ROUTE PRINT"  |--
:
:
===========================================================================
: Interface List
: 0x1 ........................... MS TCP Loopback interface
: 0x2 ...00 60 08 10 45 ba ...... 3Com 3C90x Ethernet Adapter (Microsoft's
: Packet
: Scheduler)
:
===========================================================================
:
===========================================================================
: Active Routes:
: Network Destination        Netmask          Gateway       Interface
Metric
:           0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.2
1
:         127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1
1
:       192.168.0.0    255.255.255.0      192.168.0.2     192.168.0.2
1
:       192.168.0.2  255.255.255.255        127.0.0.1       127.0.0.1
1
:     192.168.0.255  255.255.255.255      192.168.0.2     192.168.0.2
1
:         224.0.0.0        224.0.0.0      192.168.0.2     192.168.0.2
1
:   255.255.255.255  255.255.255.255      192.168.0.2     192.168.0.2
1
: Default Gateway:       192.168.0.1
:
===========================================================================
: Persistent Routes:
:   None
:
:
: --|  WINDOWS XP "IPCONFIG/ALL"  |--
:
: Windows IP Configuration
:
:         Host Name . . . . . . . . . . . . : WinXP
:         Primary Dns Suffix  . . . . . . . :
:         Node Type . . . . . . . . . . . . : Unknown
:         IP Routing Enabled. . . . . . . . : Yes
:         WINS Proxy Enabled. . . . . . . . : Yes
:
: Ethernet adapter Home:
:
:         Connection-specific DNS Suffix  . :
:         Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
: Ethernet
: Controller (3C905C-TX Compatible)
:         Physical Address. . . . . . . . . : 00-B0-D0-A4-5C-20
:         Dhcp Enabled. . . . . . . . . . . : No
:         IP Address. . . . . . . . . . . . : 192.168.0.1
:         Subnet Mask . . . . . . . . . . . : 255.255.255.0
:         IP Address. . . . . . . . . . . . :
2002:c0a8:1:4:1db2:6cde:23a7:1d0
:         IP Address. . . . . . . . . . . . :
2002:c0a8:1:4:2b0:d0ff:fea4:5c20
:         IP Address. . . . . . . . . . . . : fe80::2b0:d0ff:fea4:5c20%4
:         Default Gateway . . . . . . . . . :
:         DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
:                                             fec0:0:0:ffff::2%1
:                                             fec0:0:0:ffff::3%1
:
:
: --|  WINDOWS XP "NETSTAT -AON"  |--
:
: Active Connections
:
:   Proto  Local Address          Foreign Address        State           PID
:   TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:23             0.0.0.0:0              LISTENING       300

:   TCP    0.0.0.0:59             0.0.0.0:0              LISTENING       760
:   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       860
:   TCP    0.0.0.0:251            0.0.0.0:0              LISTENING       968
:   TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
:   TCP    0.0.0.0:1024           0.0.0.0:0              LISTENING
3492
:   TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       968
:   TCP    0.0.0.0:1027           0.0.0.0:0              LISTENING
1536
:   TCP    0.0.0.0:1030           0.0.0.0:0              LISTENING
1476
:   TCP    0.0.0.0:1033           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:1034           0.0.0.0:0              LISTENING       4
:   TCP    0.0.0.0:1080           0.0.0.0:0              LISTENING
1936
:   TCP    0.0.0.0:1504           0.0.0.0:0              LISTENING       224
:   TCP    0.0.0.0:1505           0.0.0.0:0              LISTENING       224
:   TCP    0.0.0.0:1506           0.0.0.0:0              LISTENING       224
:   TCP    0.0.0.0:1723           0.0.0.0:0              LISTENING       4
:   TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:1999           0.0.0.0:0              LISTENING       396
:   TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING       940
:   TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
1196
:   TCP    0.0.0.0:3023           0.0.0.0:0              LISTENING
1196
:   TCP    0.0.0.0:3026           0.0.0.0:0              LISTENING
1744
:   TCP    0.0.0.0:3033           0.0.0.0:0              LISTENING
1196
:   TCP    0.0.0.0:3034           0.0.0.0:0              LISTENING
4048
:   TCP    0.0.0.0:3049          
...

read more »

 
 
 

1. Win98SE Host to Win xp pro client ics won't work

I have a win98se desktop attached to the internet via a
dsl modem. I have connected to a winxp pro laptop via hpn
network. They communicate fine sharing files however I
cannot share the internet. I tried maintaining the ics
sharing of win 98se, and it will communicate however in
1/2 second the laptop (xp pro) crashes. I tried the xp
network disk and that removes ics from the win 98se
machine and they won't communicate.

2. WARNING: If your application uses dates

3. Upgrade Win 2000 Pro to Win XP Pro

4. Media Player won't stop popping open.

5. WIN XP Pro versus Win 2000 pro

6. Better Telnet client

7. Win XP Pro vs Win 2000 Pro

8. Text Capture

9. Win XP Pro versus Win 2000 Pro

10. Triple booting Win XP Pro with Win Me and Win 2000

11. ICS - XP host, 2000 Pro client doesn't work

12. Creating a Virtual IIS directory on Win 2000 hosted on XP Pro Client

13. ICS with Win XP as host and Win ME as client