Networking Forums

Networking Forums > Computer Networking > Windows Networking > Problem with multihomed servers

Reply
Thread Tools Display Modes

Problem with multihomed servers

 
 
indmrsa
Guest
Posts: n/a

 
      03-07-2007, 09:35 AM
Hi all,

I have 3 multihomed servers (2 NICs each) and two different networks:
10.1.0.XXX and 192.168.1.XXX. The first one is the corporate network. The
second one is a 1 Gb network including only the 3 servers. The purpose of
this second network is to be used for Symantec Backup Exec. So, all network
traffic of this service is on this network.

My problem is the following:

From Server2 I can ping Server3 and Server1 over both networks. However from
Server3 and Server 1 can ping Server 2 only over 10.1.0.XXX network, but not
over 192.168.1.XXX.

IP configuration in 3 machines have been done according the following:

SERVERX
NIC1 IP ADDRESS: 10.1.0.20X
NIC1 IP MASK: 255.255.255.0
NIC1 DEFAULT GATEWAY: 10.1.0.249

NIC2 IP ADDRESS: 192.168.1.X
NIC2 IP MASK: 255.255.255.0
NIC2 DEFAULT GATEWAY:

Any help will be welcome.

Regards

 
Reply With Quote
 
 
 
 
Mike Lowery
Guest
Posts: n/a

 
      03-07-2007, 04:16 PM
I would recommend creating two DNS (or hosts) entries for each server: one for
NIC1 and one for NIC2. For example:

server1-1 10.1.0.xxx
server1-2 192.168.1.xxx
server2-1 10.1.0.xxx
server2-2 192.168.1xxx
...etc..

Then you can specify which NIC to use by addressing the correct DNS host name.
I'm guessing this is your problem (or were you pinging IP addresses directly?
If so, you might need to add a static route.)

"indmrsa" <(E-Mail Removed)> wrote in message
news:BB733B96-093B-4DA3-BD6E-(E-Mail Removed)...
> Hi all,
>
> I have 3 multihomed servers (2 NICs each) and two different networks:
> 10.1.0.XXX and 192.168.1.XXX. The first one is the corporate network. The
> second one is a 1 Gb network including only the 3 servers. The purpose of
> this second network is to be used for Symantec Backup Exec. So, all network
> traffic of this service is on this network.
>
> My problem is the following:
>
> From Server2 I can ping Server3 and Server1 over both networks. However from
> Server3 and Server 1 can ping Server 2 only over 10.1.0.XXX network, but not
> over 192.168.1.XXX.
>
> IP configuration in 3 machines have been done according the following:
>
> SERVERX
> NIC1 IP ADDRESS: 10.1.0.20X
> NIC1 IP MASK: 255.255.255.0
> NIC1 DEFAULT GATEWAY: 10.1.0.249
>
> NIC2 IP ADDRESS: 192.168.1.X
> NIC2 IP MASK: 255.255.255.0
> NIC2 DEFAULT GATEWAY:
>
> Any help will be welcome.
>
> Regards
>



 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      03-07-2007, 06:12 PM
"Mike Lowery" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Then you can specify which NIC to use by addressing the correct DNS host name.
> I'm guessing this is your problem (or were you pinging IP addresses directly?
> If so, you might need to add a static route.)


Wouldn't need a static route since the nic is in the same subnet as the target
and any machine is already "aware" of networks that are "directly connected".
If setting up the DNS or Hosts names doesn't work,...then there is just more to
this story than we are being told.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------


 
Reply With Quote
 
indmrsa
Guest
Posts: n/a

 
      03-08-2007, 09:51 AM
Thank you all.

I ping the IP adresses directly.

It seems as if the windows firewall prevents the server2 from reply ping
requests. But I have checked it and it is not enabled.




"Phillip Windell" wrote:

> "Mike Lowery" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Then you can specify which NIC to use by addressing the correct DNS host name.
> > I'm guessing this is your problem (or were you pinging IP addresses directly?
> > If so, you might need to add a static route.)

>
> Wouldn't need a static route since the nic is in the same subnet as the target
> and any machine is already "aware" of networks that are "directly connected".
> If setting up the DNS or Hosts names doesn't work,...then there is just more to
> this story than we are being told.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> The views expressed (as annoying as they are, and as stupid as they sound), are
> my own and not those of my employer, or Microsoft, or anyone else associated
> with me, including my cats.
> -----------------------------------------------------
>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Linux multihomed routing (2 ISP, 1 internal network) problem andy_occ@hotmail.com Linux Networking 3 07-27-2007 03:29 PM
Problem with NTLM2 on multihomed host Peter Skvarka Windows Networking 2 08-26-2006 05:59 AM
Network Problem (Can't access game servers on Steam!) Gyuri Home Networking 0 06-28-2006 07:55 PM
Problem to sincronize 2 servers José Carretero García Windows Networking 3 07-18-2005 11:30 PM
Strange problem accessing Virgin.net servers Chris Gordon-Smith Linux Networking 4 04-16-2005 05:26 PM



1 2 3 4 5 6 7 8 9 10 11