Enabling both NICS on Server

I am trying to enable both network cards on my file server. One for the
public LAN, and one for an isolated “backup� network consisting of just
servers.

Enabling the secondary NIC on file server prevents the MAC OS X computers
from connecting to the file server. Disabling the Secondary NIC allows the
MACs to reconnect. Windows workstations can connect and use resources
correctly.
Server can not print to network printers or route out to the internet with
secondary Nic enabled.
MACs use regular TCP/IP to connect. Appletalk and File sharing for Apples is
not enabled.

Windows Server 2003 Appliance Edition SP1 (Dell PowerVault NAS O/S 3.4.9.2)

Primary NIC plugged into network switch
Secondary NIC plugged into isolated switch (for server to server backups)

Primary NIC has static domain class C IP address and configuration (DNS/WINS
& Gateway)
Secondary NIC has static class B IP address, no WINS, points to self for DNS
Neither connection is using Windows Firewall or any other firewall.

Can you help point me in the right direction to get this configured
correctly? Thanks!

That is pretty much what I would expect to happen. Enabling a second NIC
on a server usually fouls up the name resolution. Your server now has two IP
addresses associated with its name. Since most backup solutions also rely on
names to find machines, your scheme is most unlikely to work.

"Joe" <(E-Mail Removed)> wrote in message
news:A1648C8E-FA69-40F7-85E7-(E-Mail Removed)...
>I am trying to enable both network cards on my file server. One for the
> public LAN, and one for an isolated "backup" network consisting of just
> servers.
>
> Enabling the secondary NIC on file server prevents the MAC OS X computers
> from connecting to the file server. Disabling the Secondary NIC allows the
> MACs to reconnect. Windows workstations can connect and use resources
> correctly.
> Server can not print to network printers or route out to the internet with
> secondary Nic enabled.
> MACs use regular TCP/IP to connect. Appletalk and File sharing for Apples
> is
> not enabled.
>
> Windows Server 2003 Appliance Edition SP1 (Dell PowerVault NAS O/S
> 3.4.9.2)
>
> Primary NIC plugged into network switch
> Secondary NIC plugged into isolated switch (for server to server backups)
>
> Primary NIC has static domain class C IP address and configuration
> (DNS/WINS
> & Gateway)
> Secondary NIC has static class B IP address, no WINS, points to self for
> DNS
> Neither connection is using Windows Firewall or any other firewall.
>
> Can you help point me in the right direction to get this configured
> correctly? Thanks!
>

There should be no issue with making your server multihomed as you have. How
else would ISA server work? RRAS?

Is interesting what is happening when you engage the 2nd nic. No firewall
on the server causing this? Might check what changes when you engage the
nic. Route print from a wkst before and after.

Sounds like a simple config or binding issue. Bit complicated to pinpoint.

Thanks for the reply Bill!

To address the naming issue we have assigned names and ip addresses in the
servers host files. The servers work correctly for backup over the isolated
switch, but the workstation Mac OS X clients on our LAN can no longer connect
to the file server (over 1st NIC) with the second NIC enabled.

"Bill Grant" wrote:

> That is pretty much what I would expect to happen. Enabling a second NIC
> on a server usually fouls up the name resolution. Your server now has two IP
> addresses associated with its name. Since most backup solutions also rely on
> names to find machines, your scheme is most unlikely to work.
>
> "Joe" <(E-Mail Removed)> wrote in message
> news:A1648C8E-FA69-40F7-85E7-(E-Mail Removed)...
> >I am trying to enable both network cards on my file server. One for the
> > public LAN, and one for an isolated "backup" network consisting of just
> > servers.
> >
> > Enabling the secondary NIC on file server prevents the MAC OS X computers
> > from connecting to the file server. Disabling the Secondary NIC allows the
> > MACs to reconnect. Windows workstations can connect and use resources
> > correctly.
> > Server can not print to network printers or route out to the internet with
> > secondary Nic enabled.
> > MACs use regular TCP/IP to connect. Appletalk and File sharing for Apples
> > is
> > not enabled.
> >
> > Windows Server 2003 Appliance Edition SP1 (Dell PowerVault NAS O/S
> > 3.4.9.2)
> >
> > Primary NIC plugged into network switch
> > Secondary NIC plugged into isolated switch (for server to server backups)
> >
> > Primary NIC has static domain class C IP address and configuration
> > (DNS/WINS
> > & Gateway)
> > Secondary NIC has static class B IP address, no WINS, points to self for
> > DNS
> > Neither connection is using Windows Firewall or any other firewall.
> >
> > Can you help point me in the right direction to get this configured
> > correctly? Thanks!
> >
>
>
>

I noticed a routing issue and corrected the pathing. Everything is working
correctly now!
Once I unified the Gateways and Corrected an IP route everything is working.


"Joshua Bolton" wrote:

> There should be no issue with making your server multihomed as you have. How
> else would ISA server work? RRAS?
>
> Is interesting what is happening when you engage the 2nd nic. No firewall
> on the server causing this? Might check what changes when you engage the
> nic. Route print from a wkst before and after.
>
> Sounds like a simple config or binding issue. Bit complicated to pinpoint.