Re: Two networking cards
- From: "Ray" <ray@xxxxxxxx>
- Date: Tue, 11 Oct 2005 13:37:44 -0600
Wendel,
In fact, I did try tracert and said 155.57.44.0/24 could access
155.57.19.210 and could not access 155.57 19.72. Please see the following
result I tried on a computer in 155.57.44.0/24. Although I set up a gateway
(155.57.19.254) for 155.57.19.237, 44.xxx still cannot access 19.237. Please
don't be surprised 155.57.19.254 is the same router as 155.57.44.254, and I
cannot touch the router that belongs to the university.
Tracert results on a computer in 155.57.44.0/24
C:\>tracert 155.57.19.210
Tracing route to [155.57.19.210]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [155.57.19.254]
2 <1 ms <1 ms <1 ms [155.57.19.210]
Trace complete.
C:\>tracert 155.57.44.92
Tracing route to [155.57.44.92]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [155.57.44.92]
Trace complete.
C:\>tracert 155.57.44.72
Tracing route to [155.57.44.72]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms [155.57.44.72]
Trace complete.
C:\>tracert 155.57.19.237
Tracing route to [155.57.19.237]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [155.57.19.254]
2 * * * Request timed out.
Thanks.
Ray
"Wendel Hamilton" <WendelHamilton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:1FA66C41-E385-440A-943B-D317AF2F1F37@xxxxxxxxxxxxxxxx
> Ray,
> It depends where the packets are being routed.
> You really need to do some Tracert from workstation and servers in the .19
> subnet to the servers in the .44 subnet and visa versa. Also tracert
> workstation to workstation .19 to .44 subnet and visa versa. That will
> tell
> you exactly where the packets are going and what is routing them.
> It may be the dual port network card is routing packets, it shouldn't be
> so
> may be that is the problem.
> Do some trace routes and post them.
>
> "Ray" wrote:
>
>> Wendel,
>>
>> If so, it's weird, one of my servers works, the other doesn't. Is that
>> because it use a Dual-port networking card? And then is there a routing
>> in
>> the card?
>>
>> Although they are on Internet, in fact, I set up firework, only local
>> workstations can access them, so for the local network.
>>
>> Ray
>>
>> "Wendel Hamilton" <WendelHamilton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:2421F8E5-8E59-4F68-AC53-7BD5EB51C333@xxxxxxxxxxxxxxxx
>> > Ray,
>> > What I think is happening is that your routers are routing all the
>> > traffic
>> > between your subnets out through the internet and back in again. Unless
>> > you
>> > have set up RIP or static routes on your workstations. Is that the
>> > case?
>> > Use
>> > tracert to find out.
>> > Network Teaming allows multiple network cards to share a single IP
>> > address
>> > thus doubling or more your network bandwidth to the server. I don't
>> > think
>> > that's what you are after. Do you want to load balance the internet or
>> > local
>> > network?
>> >
>> >
>> > "Ray" wrote:
>> >
>> >> Yeah, the gateway of 155.57.19.0/24 for workstations and servers is
>> >> 155.57.19.254 and that of 155.57.44.0/24 is 155.57.44.254, both
>> >> gateways
>> >> are
>> >> Internet routers. We wanna use them for load balancing not for
>> >> redundancy.
>> >> Currently, it seems no routing between two cards in one server. What's
>> >> network teaming?
>> >> Thanks.
>> >>
>> >> Ray
>> >>
>> >> "Wendel Hamilton" <WendelHamilton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> message news:3A187A9D-CF70-4CD4-AED9-A7194156D682@xxxxxxxxxxxxxxxx
>> >> > Ray,
>> >> > Ok here is the thing you have a gateway of 155.57.19.254 Is this
>> >> > your
>> >> > internet router?
>> >> > do the workstations have this as their default gateway?
>> >> > What is the gateway on the workstations in your 2 subnets?
>> >> > This is key to understanding how the traffic is routed and by what.
>> >> >
>> >> > If you want performance, load balancing or redundancy then you need
>> >> > to
>> >> > use
>> >> > network teaming.
>> >> > This gives you 1 virtual IP address over multiple network cards.
>> >> >
>> >> > "Ray" wrote:
>> >> >
>> >> >> Wendel, sorry for confusion. I've given all information on 4 cards.
>> >> >> All
>> >> >> of
>> >> >> them connected Ineternet directly.
>> >> >>
>> >> >> 2 cards (in fact, it's a Dual Port card) on working one are,
>> >> >> 155.57.19.210
>> >> >> with the gateway of 155.57.19.254 and 155.57.44.92 without the
>> >> >> gateway
>> >> >> (in
>> >> >> fact, the gateway of 155.57.44.92/24 is 155.57.44.254, but the
>> >> >> gateway
>> >> >> isn't
>> >> >> set because two cards are in win2k3 ). All computers on
>> >> >> 155.57.19.0/24
>> >> >> and
>> >> >> 157.57.44.0/24 can access them (including PING, we have file
>> >> >> sharing
>> >> >> service). The OS is windows 2003 enterprise version SP1.
>> >> >>
>> >> >> 2 cards (two separate cards) on non-working one are, 155.57.19.237
>> >> >> with
>> >> >> the
>> >> >> gateway of 155.57.19.254 and 155.57.44.72 without gateway either.
>> >> >> Computers
>> >> >> on 155.57.19.0/24 can access 155.57.19.237 and those on
>> >> >> 155.57.44.0/24
>> >> >> can
>> >> >> access 155.57.44.72, but 155.57.19.0/24 cannot access 155.57.44.72,
>> >> >> vice
>> >> >> versa. The OS is windows 2003 standard version SP1.
>> >> >>
>> >> >> The networking settings of the two servers are same (at lease I
>> >> >> think),
>> >> >> is
>> >> >> there an internal routing in a Dual Port card? Does 2003 enterprise
>> >> >> support
>> >> >> more powerful on two cards? Or other setting I can configure? I
>> >> >> never
>> >> >> set
>> >> >> up
>> >> >> a server with two cards before, so confused.
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >> Ray
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Wendel Hamilton" <WendelHamilton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> >> >> in
>> >> >> message news:366AE4E2-5772-4697-8A12-8436E517F130@xxxxxxxxxxxxxxxx
>> >> >> > Ray,
>> >> >> > Need more information on the physical topology
>> >> >> > You have described only 2 out of the 4 network cards.
>> >> >> > Is it?
>> >> >> > <internet>---<nic2 155.57.19.0/24 server1
>> >> >> > nic1xxx.xxx.xxx.yyy/24>----,
>> >> >> >
>> >> >> > }------<Workstations xxx.xxx.xxx.0/24>
>> >> >> > <internet>---<nic2 155.57.44.0/24 server2 nic1
>> >> >> > xxx.xxx.xxx.yyy/24>----'
>> >> >> >
>> >> >> > or
>> >> >> > <internet>---<nic2 xxx.xxx.xxx.xxx server1 nic1
>> >> >> > 155.57.19.0/24>----,
>> >> >> >
>> >> >> > }------<workstations>
>> >> >> > <internet>---<nic2 xxx.xxx.xxx.xxx server2 nic1
>> >> >> > 155.57.44.0/24>----'
>> >> >> >
>> >> >> > or
>> >> >> > <internet>---<nic2 xxx.xxx.xxx.xxx server1 nic1
>> >> >> > 155.57.19.0/24>-------<workstations>
>> >> >> >
>> >> >> >
>> >> >> > <internet>---<nic2 xxx.xxx.xxx.xxx server2 nic1
>> >> >> > 155.57.44.0/24>-------<workstations>
>> >> >> >
>> >> >> > or
>> >> >> > ,---<nic2 xxx.xxx.xxx.xxx
>> >> >> > server1
>> >> >> > nic1
>> >> >> > 155.57.19.0/24>-------<workstations>
>> >> >> > <internet>-<Router>-{
>> >> >> >
>> >> >> > ' --<nic2 xxx.xxx.xxx.xxx
>> >> >> > server2
>> >> >> > nic1
>> >> >> > 155.57.44.0/24>-------<workstations>
>> >> >> >
>> >> >> >
>> >> >> > "Ray" wrote:
>> >> >> >
>> >> >> >> Hi there,
>> >> >> >>
>> >> >> >> Here is an interesting question. We have two servers, each of
>> >> >> >> them
>> >> >> >> has
>> >> >> >> two
>> >> >> >> networking cards, all of them connect Internet directly (two
>> >> >> >> subnets,
>> >> >> >> 155.57.19.xxx and 155.57.44.xxx), but only cards on
>> >> >> >> 155.57.19.xxx
>> >> >> >> sets
>> >> >> >> up
>> >> >> >> a
>> >> >> >> gateway, 155.57.19.254. My question is both cards on one of
>> >> >> >> servers
>> >> >> >> work
>> >> >> >> very well, computers on both subnets 155.57.19.xxx and
>> >> >> >> 155.57.44.xxx
>> >> >> >> can
>> >> >> >> access both cards, but one card on the other server works not
>> >> >> >> well,
>> >> >> >> computers on 155.57.44.xxx can access 155.57.44.72, computers on
>> >> >> >> 155.57.19.xxx can access 155.57.19.237, but computers on
>> >> >> >> 155.57.19.xxx
>> >> >> >> cannot access 155.57.44.72.
>> >> >> >>
>> >> >> >> Configuration of working one as
>> >> >> >> Windows 2003 Enterprise Version SP1
>> >> >> >> An Intel dual port networking card
>> >> >> >>
>> >> >> >> Configuration of non-working one as
>> >> >> >> Windows 2003 Standard Version SP1
>> >> >> >> One Intel(R) PRO/1000 XT Network Connection and one Intel(R)
>> >> >> >> PRO/100 S
>> >> >> >> Server Adapter
>> >> >> >>
>> >> >> >> I don't know why one of them doesn't work. Is it networking
>> >> >> >> configuration
>> >> >> >> problem, Windows 2k3 version problem or networking card problem?
>> >> >> >> In
>> >> >> >> fact,
>> >> >> >> I
>> >> >> >> cannot figure out both two networking card connecting with
>> >> >> >> Internet.
>> >> >> >>
>> >> >> >> Please see the attached route tables, the top one is from
>> >> >> >> working
>> >> >> >> server,
>> >> >> >> the bottom one is from non-working server.
>> >> >> >>
>> >> >> >> Thanks.
>> >> >> >>
>> >> >> >> Ray
>> >> >> >>
>> >> >> >> IPv4 Route Table
>> >> >> >> ===========================================================================
>> >> >> >> Interface List
>> >> >> >> 0x1 ........................... MS TCP Loopback interface
>> >> >> >> 0x10003 ...00 07 b3 2c d6 04 ...... Intel(R) PRO/1000 MT Dual
>> >> >> >> Port
>> >> >> >> Server
>> >> >> >> Adapte
>> >> >> >> r
>> >> >> >> 0x10004 ...00 07 b3 2c d6 05 ...... Intel(R) PRO/1000 MT Dual
>> >> >> >> Port
>> >> >> >> Server
>> >> >> >> Adapte
>> >> >> >> r #2
>> >> >> >> ===========================================================================
>> >> >> >> ===========================================================================
>> >> >> >> Active Routes:
>> >> >> >> Network Destination Netmask Gateway
>> >> >> >> Interface
>> >> >> >> Metric
>> >> >> >> 0.0.0.0 0.0.0.0 155.57.19.254
>> >> >> >> 155.57.19.210
>> >> >> >> 1
>> >> >> >> 127.0.0.0 255.0.0.0 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 1
>> >> >> >> 155.57.19.0 255.255.255.0 155.57.19.210
>> >> >> >> 155.57.19.210
>> >> >> >> 1
>> >> >> >> 155.57.19.210 255.255.255.255 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 1
>> >> >> >> 155.57.44.0 255.255.255.0 155.57.44.92
>> >> >> >> 155.57.44.92
>> >> >> >> 10
>> >> >> >> 155.57.44.92 255.255.255.255 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 10
>> >> >> >> 155.57.255.255 255.255.255.255 155.57.19.210
>> >> >> >> 155.57.19.210
>> >> >> >> 1
>> >> >> >> 155.57.255.255 255.255.255.255 155.57.44.92
>> >> >> >> 155.57.44.92
>> >> >> >> 10
>> >> >> >> 224.0.0.0 240.0.0.0 155.57.19.210
>> >> >> >> 155.57.19.210
>> >> >> >> 1
>> >> >> >> 224.0.0.0 240.0.0.0 155.57.44.92
>> >> >> >> 155.57.44.92
>> >> >> >> 10
>> >> >> >> 255.255.255.255 255.255.255.255 155.57.19.210
>> >> >> >> 155.57.19.210
>> >> >> >> 1
>> >> >> >> 255.255.255.255 255.255.255.255 155.57.44.92
>> >> >> >> 155.57.44.92
>> >> >> >> 1
>> >> >> >> Default Gateway: 155.57.19.254
>> >> >> >> ===========================================================================
>> >> >> >> Persistent Routes:
>> >> >> >> None
>> >> >> >>
>> >> >> >>
>> >> >> >> IPv4 Route Table
>> >> >> >> ===========================================================================
>> >> >> >> Interface List
>> >> >> >> 0x1 ........................... MS TCP Loopback interface
>> >> >> >> 0x30004 ...00 02 e5 c2 3f fc ...... Intel(R) PRO/100 S Server
>> >> >> >> Adapter
>> >> >> >> 0x30005 ...00 06 3e f2 ec c4 ...... Intel(R) PRO/1000 XT Network
>> >> >> >> Connection
>> >> >> >> ===========================================================================
>> >> >> >> ===========================================================================
>> >> >> >> Active Routes:
>> >> >> >> Network Destination Netmask Gateway
>> >> >> >> Interface
>> >> >> >> Metric
>> >> >> >> 0.0.0.0 0.0.0.0 155.57.19.254
>> >> >> >> 155.57.19.237
>> >> >> >> 1
>> >> >> >> 127.0.0.0 255.0.0.0 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 1
>> >> >> >> 155.57.19.0 255.255.255.0 155.57.19.237
>> >> >> >> 155.57.19.237
>> >> >> >> 1
>> >> >> >> 155.57.19.237 255.255.255.255 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 1
>> >> >> >> 155.57.44.0 255.255.255.0 155.57.44.72
>> >> >> >> 155.57.44.72
>> >> >> >> 20
>> >> >> >> 155.57.44.72 255.255.255.255 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 20
>> >> >> >> 155.57.255.255 255.255.255.255 155.57.19.237
>> >> >> >> 155.57.19.237
>> >> >> >> 1
>> >> >> >> 155.57.255.255 255.255.255.255 155.57.44.72
>> >> >> >> 155.57.44.72
>> >> >> >> 20
>> >> >> >> 224.0.0.0 240.0.0.0 155.57.19.237
>> >> >> >> 155.57.19.237
>> >> >> >> 1
>> >> >> >> 224.0.0.0 240.0.0.0 155.57.44.72
>> >> >> >> 155.57.44.72
>> >> >> >> 20
>> >> >> >> 255.255.255.255 255.255.255.255 155.57.19.237
>> >> >> >> 155.57.19.237
>> >> >> >> 1
>> >> >> >> 255.255.255.255 255.255.255.255 155.57.44.72
>> >> >> >> 155.57.44.72
>> >> >> >> 1
>> >> >> >> Default Gateway: 155.57.19.254
>> >> >> >> ===========================================================================
>> >> >> >> Persistent Routes:
.
- Follow-Ups:
- Re: Two networking cards
- From: Wendel Hamilton
- Re: Two networking cards
- References:
- Two networking cards
- From: Ray
- Re: Two networking cards
- From: Ray
- Re: Two networking cards
- From: Wendel Hamilton
- Re: Two networking cards
- From: Ray
- Re: Two networking cards
- From: Wendel Hamilton
- Re: Two networking cards
- From: Ray
- Re: Two networking cards
- From: Wendel Hamilton
- Two networking cards
- Prev by Date: remote desktop, client initiated?
- Next by Date: Re: Two networking cards
- Previous by thread: Re: Two networking cards
- Next by thread: Re: Two networking cards
- Index(es):
Relevant Pages
|
