2 Nics, 1 LAN 1 Internet

Been a long time since Ive been here, but maybe someone can hlep me out.

I have 2 network cards,

1 has a ip of 113.1.1.245, subnet of 255.0.0.0
2 has a ip of 115.1.1.245 subnet of 255.255.255.0

now I want to make the 2nd one the one that accepts HTTP connections. the first one has a lan connection to our SQL server, mail server... etc..etc... but the 2nd one has the http ip.

Both are hooked up to seperate PIX 515e fireawalls. and the problem with haveing them on the same network card is that the IP' are in total different lands, first set are 72's and the others are 145's

Possible?

Thanks
LVL 14
B_DorseyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

masnrockCommented:
I see what you're trying, but don't think that would work. Problem would be when the server tries to communicate with any clients... you could be in for some pretty ugly surprises. However, that *might* have a shot at working if you were using virtual machines via products like VMware or Virtual PC, but I don't remember anymore about that.
adamdrayerCommented:

It really depends on how big your internal network is.  Only one card should have a gateway, and the other should not. (blank).  Then all traffic that is not on the local subnets will be sent to the gateway unless it has a specific route.  This means that you could create routes for all your internal LAN traffic that uses the next hop on the 133.0.0.0 as the gateway.  But the 2nd NIC would be the one with the "default gateway".  This way all your internal traffic would be routed over the 1st NIC and all other traffic would be routed over the 2nd.

You create static routes by using the ROUTE command.  add the "-p" for to make the routes permanent.  Although managing static routes is not recommended on the client machine, sometimes it is nescessary.

Alternatively, you could join the two networks PIXs with a router.  Then you could plug the client into a 3rd router interface or a switch that has one of the router interfaces and PIXs attached to it.  This way the router can be used to route the information.

It all really depends on how scalable you would like this solution.  Is it just for one machine or are you planning on doing it for more than that?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
B_DorseyAuthor Commented:
you mean this was as SIMPLE AS REMOVING THE DAMN GATEWAY..... LOL

Ive been stuck on this stupid problem for like 4 weeks now.... it was hit or miss for me, i would enable one, disable the other and sometimes it would work, and hoped we didnt need to reset...lol

Wow you are my most favorite person in the whole WORLD....

 :)
 :)
 :)
 :)

THANKS, THANKS, THANKS!!!!!!!


b
adamdrayerCommented:
hey no problem!   Glad to hear you got it working ok!  Thanks for all your kind words!  =)

Just make sure you don't have any local subnets outside the range 113.x.x.x that you want routed through NIC1.  
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.