Crosswire two servers

Hi,

I'm trying to improve data transfer between two of my w2k3 servers.
Circumventing my 100Mbps switches I've installed second 1gigbyte NICs in both
machines and a crosswire patch cable linking the two. The hardware
installation went smoothly and both show 1gig connections established. Next
step was to set up routing so that only traffic originating on each machine
would move between the two interfaces. Unfortunately all traffic is still
going through the old 100Mbps route. I've copied the routing table below.
Two IPs I'm trying to linke are 192.168.0. 220 and 192.168.0.151. The other
server has the same route added (except reversed and interface 0x10004).
Anything that will help alliviate my confusion gratefully received.

Thanks,

Steve

IPv4 Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network Connection
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151 10
0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150 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.150 192.168.0.150 1
192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151 10
192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151 1
192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150 1
192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151 10
224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150 1
224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151 10
255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150 1
255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151 1
Default Gateway: 192.168.0.5
================================================== =========================
Persistent Routes:
None

Y:\>route add 192.168.0.220 MASK 255.255.255.255 192.168.0.220 METRIC 1 IF
0x20004

:\>route print

IPv4 Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network Connection
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151 10
0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150 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.150 192.168.0.150 1
192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151 10
192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151 1
192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150 1
192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151 10
224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150 1
224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151 10
255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150 1
255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151 1
Default Gateway: 192.168.0.5
================================================== =========================
Persistent Routes:
None

Y:\>route add 192.168.0.220 MASK 255.255.255.255 192.168.0.220 METRIC 1 IF
0x20004

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\administrator.SCBC>route print

IPv4 Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network Connection
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151 10
0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150 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.150 192.168.0.150 1
192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151 10
192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151 1
192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150 1
192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151 10
224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150 1
224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151 10
255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150 1
255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151 1
Default Gateway: 192.168.0.5
================================================== =========================
Persistent Routes:
None

C:\>ipconfig /all

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-0C-F1-6E-10-68
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.150
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.5
DNS Servers . . . . . . . . . . . : 192.168.0.100
192.168.0.150

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection
Physical Address. . . . . . . . . : 00-0C-F1-6E-10-67
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.151
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.5
DNS Servers . . . . . . . . . . . : 192.168.0.100
192.168.0.150

The whole concept of what you are trying to do is flawed and just isn't
going to work.

1. Forget the two Nics in the Servers.
2. Replace the existing 100mbps Nics with 1000mbps Nics. (*one* Nic and
*one* IP# per server).
3. Replace the Switch they connect to with either a Gigabit Switch or a
100mbps switch with add-on modules to gain at least two Gigabit ports.
4. Replace the patch cables with higher quality cables designed for the
Gigabit speed if you need to.
5. Run the Servers off of those two ports.
6. The switch itself will isolate the traffic from the rest of the
LAN,...that is what switches do.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"Steve Young" <(E-Mail Removed)> wrote in message
news:A3AEC2CA-CC9A-487C-8A7D-(E-Mail Removed)...
> Hi,
>
> I'm trying to improve data transfer between two of my w2k3 servers.
> Circumventing my 100Mbps switches I've installed second 1gigbyte NICs in
both
> machines and a crosswire patch cable linking the two. The hardware
> installation went smoothly and both show 1gig connections established.
Next
> step was to set up routing so that only traffic originating on each
machine
> would move between the two interfaces. Unfortunately all traffic is still
> going through the old 100Mbps route. I've copied the routing table below.
> Two IPs I'm trying to linke are 192.168.0. 220 and 192.168.0.151. The
other
> server has the same route added (except reversed and interface 0x10004).
> Anything that will help alliviate my confusion gratefully received.
>
> Thanks,
>
> Steve
>
> IPv4 Route Table
>
================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
> 0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network
Connection
>
================================================== =========================
>
================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
Metric
> 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151
10
> 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150
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.150 192.168.0.150
1
> 192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151
10
> 192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1
1
> 192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1
10
> 192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151
1
> 192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150
1
> 192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151
10
> 224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150
1
> 224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151
10
> 255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150
1
> 255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151
1
> Default Gateway: 192.168.0.5
>
================================================== =========================
> Persistent Routes:
> None
>
> Y:\>route add 192.168.0.220 MASK 255.255.255.255 192.168.0.220 METRIC 1 IF
> 0x20004
>
> :\>route print
>
> IPv4 Route Table
>
================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
> 0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network
Connection
>
================================================== =========================
>
================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
Metric
> 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151
10
> 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150
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.150 192.168.0.150
1
> 192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151
10
> 192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1
1
> 192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1
10
> 192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151
1
> 192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150
1
> 192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151
10
> 224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150
1
> 224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151
10
> 255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150
1
> 255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151
1
> Default Gateway: 192.168.0.5
>
================================================== =========================
> Persistent Routes:
> None
>
> Y:\>route add 192.168.0.220 MASK 255.255.255.255 192.168.0.220 METRIC 1 IF
> 0x20004
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\administrator.SCBC>route print
>
> IPv4 Route Table
>
================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
> 0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network
Connection
>
================================================== =========================
>
================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
Metric
> 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151
10
> 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150
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.150 192.168.0.150
1
> 192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151
10
> 192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1
1
> 192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1
10
> 192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151
1
> 192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150
1
> 192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151
10
> 224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150
1
> 224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151
10
> 255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150
1
> 255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151
1
> Default Gateway: 192.168.0.5
>
================================================== =========================
> Persistent Routes:
> None
>
> C:\>ipconfig /all
>
> Windows IP Configuration
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
> Physical Address. . . . . . . . . : 00-0C-F1-6E-10-68
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.150
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.5
> DNS Servers . . . . . . . . . . . : 192.168.0.100
> 192.168.0.150
>
> Ethernet adapter Local Area Connection 2:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network
Connection
> Physical Address. . . . . . . . . : 00-0C-F1-6E-10-67
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.151
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.5
> DNS Servers . . . . . . . . . . . : 192.168.0.100
> 192.168.0.150
>
>

Hi Phillip,

Thanks for the response. Is there really no way to make this work? I'm
employed by a small a charity so $ is an issue. Hence the experiment with
NiCs and crosswire patch cable. No-one is about to give me money for a new
switch sadly.

Steve

"Phillip Windell" wrote:

> The whole concept of what you are trying to do is flawed and just isn't
> going to work.
>
> 1. Forget the two Nics in the Servers.
> 2. Replace the existing 100mbps Nics with 1000mbps Nics. (*one* Nic and
> *one* IP# per server).
> 3. Replace the Switch they connect to with either a Gigabit Switch or a
> 100mbps switch with add-on modules to gain at least two Gigabit ports.
> 4. Replace the patch cables with higher quality cables designed for the
> Gigabit speed if you need to.
> 5. Run the Servers off of those two ports.
> 6. The switch itself will isolate the traffic from the rest of the
> LAN,...that is what switches do.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
> "Steve Young" <(E-Mail Removed)> wrote in message
> news:A3AEC2CA-CC9A-487C-8A7D-(E-Mail Removed)...
> > Hi,
> >
> > I'm trying to improve data transfer between two of my w2k3 servers.
> > Circumventing my 100Mbps switches I've installed second 1gigbyte NICs in
> both
> > machines and a crosswire patch cable linking the two. The hardware
> > installation went smoothly and both show 1gig connections established.
> Next
> > step was to set up routing so that only traffic originating on each
> machine
> > would move between the two interfaces. Unfortunately all traffic is still
> > going through the old 100Mbps route. I've copied the routing table below.
> > Two IPs I'm trying to linke are 192.168.0. 220 and 192.168.0.151. The
> other
> > server has the same route added (except reversed and interface 0x10004).
> > Anything that will help alliviate my confusion gratefully received.
> >
> > Thanks,
> >
> > Steve
> >
> > IPv4 Route Table
> >
> ================================================== =========================
> > Interface List
> > 0x1 ........................... MS TCP Loopback interface
> > 0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
> > 0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network
> Connection
> >
> ================================================== =========================
> >
> ================================================== =========================
> > Active Routes:
> > Network Destination Netmask Gateway Interface
> Metric
> > 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151
> 10
> > 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150
> 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.150 192.168.0.150
> 1
> > 192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151
> 10
> > 192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1
> 1
> > 192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1
> 10
> > 192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151
> 1
> > 192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150
> 1
> > 192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151
> 10
> > 224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150
> 1
> > 224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151
> 10
> > 255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150
> 1
> > 255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151
> 1
> > Default Gateway: 192.168.0.5
> >
> ================================================== =========================
> > Persistent Routes:
> > None
> >
> > Y:\>route add 192.168.0.220 MASK 255.255.255.255 192.168.0.220 METRIC 1 IF
> > 0x20004
> >
> > :\>route print
> >
> > IPv4 Route Table
> >
> ================================================== =========================
> > Interface List
> > 0x1 ........................... MS TCP Loopback interface
> > 0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
> > 0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network
> Connection
> >
> ================================================== =========================
> >
> ================================================== =========================
> > Active Routes:
> > Network Destination Netmask Gateway Interface
> Metric
> > 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151
> 10
> > 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150
> 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.150 192.168.0.150
> 1
> > 192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151
> 10
> > 192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1
> 1
> > 192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1
> 10
> > 192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151
> 1
> > 192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150
> 1
> > 192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151
> 10
> > 224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150
> 1
> > 224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151
> 10
> > 255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150
> 1
> > 255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151
> 1
> > Default Gateway: 192.168.0.5
> >
> ================================================== =========================
> > Persistent Routes:
> > None
> >
> > Y:\>route add 192.168.0.220 MASK 255.255.255.255 192.168.0.220 METRIC 1 IF
> > 0x20004
> >
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> > C:\Documents and Settings\administrator.SCBC>route print
> >
> > IPv4 Route Table
> >
> ================================================== =========================
> > Interface List
> > 0x1 ........................... MS TCP Loopback interface
> > 0x10003 ...00 0c f1 6e 10 68 ...... Intel(R) PRO/100 VE Network Connection
> > 0x20004 ...00 0c f1 6e 10 67 ...... Intel(R) PRO/1000 CT Network
> Connection
> >
> ================================================== =========================
> >
> ================================================== =========================
> > Active Routes:
> > Network Destination Netmask Gateway Interface
> Metric
> > 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.151
> 10
> > 0.0.0.0 0.0.0.0 192.168.0.5 192.168.0.150
> 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.150 192.168.0.150
> 1
> > 192.168.0.0 255.255.255.0 192.168.0.151 192.168.0.151
> 10
> > 192.168.0.150 255.255.255.255 127.0.0.1 127.0.0.1
> 1
> > 192.168.0.151 255.255.255.255 127.0.0.1 127.0.0.1
> 10
> > 192.168.0.220 255.255.255.255 192.168.0.151 192.168.0.151
> 1
> > 192.168.0.255 255.255.255.255 192.168.0.150 192.168.0.150
> 1
> > 192.168.0.255 255.255.255.255 192.168.0.151 192.168.0.151
> 10
> > 224.0.0.0 240.0.0.0 192.168.0.150 192.168.0.150
> 1
> > 224.0.0.0 240.0.0.0 192.168.0.151 192.168.0.151
> 10
> > 255.255.255.255 255.255.255.255 192.168.0.150 192.168.0.150
> 1
> > 255.255.255.255 255.255.255.255 192.168.0.151 192.168.0.151
> 1
> > Default Gateway: 192.168.0.5
> >
> ================================================== =========================
> > Persistent Routes:
> > None
> >
> > C:\>ipconfig /all
> >
> > Windows IP Configuration
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
> Connection
> > Physical Address. . . . . . . . . : 00-0C-F1-6E-10-68
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.0.150
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.0.5
> > DNS Servers . . . . . . . . . . . : 192.168.0.100
> > 192.168.0.150
> >
> > Ethernet adapter Local Area Connection 2:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network
> Connection
> > Physical Address. . . . . . . . . : 00-0C-F1-6E-10-67
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.0.151
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.0.5
> > DNS Servers . . . . . . . . . . . : 192.168.0.100
> > 192.168.0.150
> >
> >
>
>
>

"Steve Young" <(E-Mail Removed)> wrote in message
news:3B3A8175-1C64-4B3E-B3B9-(E-Mail Removed)...
> Thanks for the response. Is there really no way to make this work?

No. Nothing that doesn't create a huge complicated difficult to manage mess.

> I'm
> employed by a small a charity so $ is an issue. Hence the experiment with
> NiCs and crosswire patch cable. No-one is about to give me money for a
new
> switch sadly.

They don't cost that much. You can get a small 4 or 8 port gigabit switch at
the nearest BesBuy, Circuit City, whatever,..probably for less than
$100,..which is about the price of two tank fulls of gas now-a-days. You
Cat5 patch cables are probably already fine.

If this is that low-budget of an outfit, then your network propbably isn't
big enough or generating enough traffic to have to worry about the whole
entire thing you are considering in the first place. We are an affiate TV
News Station with around 100 units on the local LAN at this one site (over
20 sites total) and my 100mbps network isn't even breathing hard.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

Thanks Phillip,

Didn't know you could get 4 and 8 port gigabyte switches. That sounds like a
solution. Traffic only get jammed on my network when I want to shift a 75Gig
backup file during the day. Not something I choose to do often, but ntbackup
stalls frequently enough to make it necessary sometimes.

Cheers,

Steve

"Phillip Windell" wrote:

> "Steve Young" <(E-Mail Removed)> wrote in message
> news:3B3A8175-1C64-4B3E-B3B9-(E-Mail Removed)...
> > Thanks for the response. Is there really no way to make this work?
>
> No. Nothing that doesn't create a huge complicated difficult to manage mess.
>
> > I'm
> > employed by a small a charity so $ is an issue. Hence the experiment with
> > NiCs and crosswire patch cable. No-one is about to give me money for a
> new
> > switch sadly.
>
> They don't cost that much. You can get a small 4 or 8 port gigabit switch at
> the nearest BesBuy, Circuit City, whatever,..probably for less than
> $100,..which is about the price of two tank fulls of gas now-a-days. You
> Cat5 patch cables are probably already fine.
>
> If this is that low-budget of an outfit, then your network propbably isn't
> big enough or generating enough traffic to have to worry about the whole
> entire thing you are considering in the first place. We are an affiate TV
> News Station with around 100 units on the local LAN at this one site (over
> 20 sites total) and my 100mbps network isn't even breathing hard.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
>
>