Re: Two networking cards

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:
>> None
>>
>>
>>


.

Relevant Pages

  • Re: FC3 upgrade - X is hosed :( (LONG)
    ... >>and the i815 driver is loaded per normal as far as I can tell. ... > Regards, Mike Klinke ... This caused the server to not even come ... Code was changed to get the 810/815 video cards to work again. ...
    (Fedora)
  • Re: Networked raid storage and NFS
    ... You can buy these chassis with hot swap SATA sleds, and the 3ware cards support auto detection when a drive is changed out. ... You can pretty much build anything from a 500GB to 15TB server in one chassis out of these. ... The Open-E solution turns your commodity x86 box into a SAN or NAS server, ...
    (comp.arch.storage)
  • linux server hardware
    ... I am looking at setting up a linux server (will run accounting package, ... Should I be looking at SCSI? ... out there with onboard SCSI, and the PCI SCSI cards, well they're pretty ...
    (comp.os.linux.hardware)
  • Re: Server side encryption - Newbie
    ... terminal emulator. ... I think the smart cards are a great idea, but it is doubtful they would ... to encrypt any sensitive LAN traffic, ... What language is the server app written in? ...
    (sci.crypt)
  • DHCP and DNS issues
    ... 2000 server with 2 network cards and is DC. ... This machines has 2 network cards in it. ... DNS Server has updated its own host records. ...
    (microsoft.public.win2000.networking)