From: "Thees Peereboom" 

Geo,

---------------startquote

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface 0x2 ...00 30 4f
15 bf 4f ...... NDIS 5.0 driver
(Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
           0.0.0.0          0.0.0.0      192.168.0.9    192.168.0.17      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.17    192.168.0.17      1
      192.168.0.17  255.255.255.255        127.0.0.1       127.0.0.1      1
     192.168.0.255  255.255.255.255     192.168.0.17    192.168.0.17      1
         224.0.0.0        224.0.0.0     192.168.0.17    192.168.0.17      1
   255.255.255.255  255.255.255.255     192.168.0.17    192.168.0.17      1
Default Gateway:       192.168.0.9
===========================================================================
Persistent Routes:
   None
---------------endquote

- Thees Peereboom


On Thu, 19 Aug 2004 18:52:28 -0400, Geo.  wrote:

> "John Beckett" 
wrote in message
> news:41248d8f.6537951{at}216.144.1.254...
>
>> Hmmm. Since you have a strange situation, I will mention an unlikely
>> scenario. If the operating system has some settings for the old NIC, it
>> may try to use it to reach some destinations.
>
> Oh good idea, Thees, on WS1 type
>
> route print
>
> and post the results.
>
> Geo.
>
>

--- BBBS/NT v4.01 Flag-5