Re: Crosswire two servers

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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/ISA2004_AccessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
> http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
> "Steve Young" <SteveYoung@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A3AEC2CA-CC9A-487C-8A7D-8B38CCE60DE1@xxxxxxxxxxxxxxxx
> > 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
> >
> >
>
>
>
.

Relevant Pages

  • Re: Problem on 2 NICs
    ... The servers are connected to the same switch (the ... switch has 2 VLANs, but both servers are on the same ... This connection is for workstations to talk to the ...
    (microsoft.public.windows.server.general)
  • Re: Segregated Switch Ports
    ... servers and leave them on the Public Network Edge like that. ... and they each have two NICs. ... our cable connection and the other assigned to our DSL, ... different physical switch to prevent confusion in the ARP tables that ...
    (microsoft.public.windows.server.networking)
  • Re: Odd Networking Issue: Windows vs Linux
    ... But then on servers that are fast at home are actually ... Much depends on from where yuor school gets its connection, ... Switches would be in the network "very close" to the machines - that is, ... if the switch is of any quality, ...
    (comp.os.linux.networking)
  • Segregated Switch Ports
    ... Right now I have 7 servers in a rack ... and they each have two NICs. ... our cable connection and the other assigned to our DSL, ... different physical switch to prevent confusion in the ARP tables that ...
    (microsoft.public.windows.server.networking)
  • Re: Unbuilt sections of numbered routes
    ... I'm curious about routes ... highway system and most of the gaps are in rural areas. ... Probably never will be built. ... demands a connection to US 81, but I doubt it will ever happen. ...
    (misc.transport.road)