Splitting NIC cards into 2 vlans 1 for RDP and other for SERVER to server

I have a situation where I would like to utilitize the 2 nic cards on my hp
dl380 server to isolate traffic and improve performance. All of our users
here use a thin client PC via linux cdrom boot software to RDP into our 2003
terminal servers. These servers than talk to our database server when
running applications. What I would like to do is split the nic card on the
terminal server so that RDP traffic and regular user traffic flows thru 1
and the other is use to communicate to the DB server. We already have VLANS
set on different ip segments for our servers and the RDP users.

Servers vlan is 10.73.10.x where TS server is 10.73.10.11 and my DB server
is 10.73.10.5
my RDP thin client users vlan is 10.73.30.50 - 10.73.30.254

What I am thinking is to split the teamed nics and assign 1 nic to
10.73.30.11 and leave the other as 10.73.10.11
Now when users RDP to the server they will use the dns entry for 10.73.30.11
not 10.73.10.11. This will then elimiate a hop on my layer 3 switch since
they are on the same subnet.

My question is since the server has 1 netbios name what IP will be assigned
to that, the .10 or .30 segment. I will still like the netbios name to be
assigned to the 10.73.10.11 original address.

Also how can I the TS server to use the other nic directly to get to the .10
segment so that every packet requiring to get to the .10 segment does not
leave the server on the .30 nic and hit our layer 3 switch to get to the .10
segment and back.

Thanks

 

If there is no current overloading of the "path" in use now,..then you are
trying to solve an imaginary problem that does not exist.

Nebios can be a mess.

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611

Here are some other considerations:

Microsoft Windows XP - Multihoming Considerations
http://www.microsoft.com/resources/documentation/windows/xp/all/reskit/en-us/prcc_tcp_qpzj.asp?

159168 - Multiple Default Gateways Can Cause Connectivity Problems
http://support.microsoft.com/kb/159168/EN-US/