Sorry Matt,
Haven't checked the group for a couple days.
You are correct, each interface should have it's own router (gateway)
address to handle the traffic. However, the "server" should only have one
default gateway. If the server has incoming traffic on one of the interfaces
(the .net INT for example) and the .com interface was enabled last, it's
going to try to respond to that incoming traffic using the default dateway
route that is highest on the routing table.
Open a command window, and type route print.
You should see something like this:
U:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 0d 9d 5d 62 d7 ...... National Semiconductor Corp. DP83815
10/10
0 MacPhyter3v PCI Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.31.3.254 10.31.2.150 1
10.31.2.0 255.255.254.0 10.31.2.150 10.31.2.150 1
10.31.2.150 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.31.2.150 10.31.2.150 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.31.2.150 10.31.2.150 1
255.255.255.255 255.255.255.255 10.31.2.150 10.31.2.150 1
Default Gateway: 10.31.3.254
===========================================================================
Persistent Routes:
None
If you have two default gateway address lines (example: 0.0.0.0 0.0.0.0
[gateway] [int]) the server is going to choose arbitrarily which
interface on which to respond.
When I set up a mulitihomed box, I usually have one NIC with a default
gateway address for the server (all traffic will use this interface if the
destination is not on the local segment, as its default) and then manually
add another route specifically mapping to the other Int's addr space.
I don't know all the details of your configuration, and this may not be the
solution you are looking for, but is one router (addr space)public and the
other private? If so, it's an easy fix. If both interfaces are publicly
facing, there may be a better way to configure the flow of traffic and the
router.
Type Route /? at a command prompt and look at the syntax to set up the
routing tables on the server.
Use Route Add and Route Delete to modify the routing table and make the
route destined for a specific space persistent or you'll lose it on next
reboot.
Hope this helps Matt.
Regards,
Mark
(e-mail address removed)
replace no spam with hotmail to contact me.
Hi Mark,
The ftp server is setup to use the correct NIC. The
software I am using is Serv-U and it shows the correct IP.
I am confused on the gateway problem, as I have two
routers. Router A handles the .com domain and Router B
handles the .net domain. So one card needs Router A to be
it's gateway, and the other needs Router B to be the
gateway does it not?
Also how would I set the routing table? What you are
describe sounds like you have the problem figured.
I appreciate the help, and appologize if I haven't
answered completely (I am a programmer and not a network
tech, so I am out in left field at the moment).
Matt
-----Original Message-----
Do you have your default FTP site bound to the NIC you want? If it's set to
all unassigned, it will take whichever card it available.
Also, with your two NICs, you should only have one default gateway for the
box (not one for each card). If you have two default gateways, whichever
card is initiated or enabled last, wins. There should only be one 0.0.0.0
0.0.0.0 [gateway] config line in your routing table.
if you need to have a static route for the second card, manually add it to
your routing table and make it persistent (so it will stay after a reboot)..
Hope this helps.
Mark
Hi,
I have a server setup with two network cards.
One has a static IP for our domain (e.g. abc.net). The
other is behind a router that that uses our main static IP
(e.g. abc.com).
Both cards work to surf the net (I can unplug either and
still be connected).
My problem is that I have a ftp server running on this
machine and it uses the main IP (abc.com). If I unplug
the new IP (abc.net), the ftp server works. When I plug
the new IP (abc.net) back in, it stops working.
This machine originally only sat behind the router. It's
only in the last few days that I have been trying to add
the new (abc.net).
So, does anyone have an idea of what I might be doing
wrong with my configuration. It seems like the cards are
conflicting with one another.
Any help is greatly appreciated,
Matt
.
