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


Hi,

Please post this query in microsoft.public.windows.server.networking also.

--
Thanks,
Priya.

http://blogs.msdn.com/ts
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jerry Alan Braga" <jerry.braga@xxxxxxxxxxx> wrote in message news:%23PfwXAO8JHA.5424@xxxxxxxxxxxxxxxxxxxxxxx
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


.

Relevant Pages

  • Re: Is this net traffic normal?
    ... accept RDP and connect to them from the server. ... Something worth checking at this point is that neither the SBS nor any workstation have any DNS server configured other than the LAN IP address of the SBS. ... You may have eliminated most of the workstations, but you can't remove the SBS, and worth remembering that many NICs have their transceivers powered even with the computer off, see below. ...
    (microsoft.public.windows.server.sbs)
  • RE: Splitting NIC cards into 2 vlans 1 for RDP and other for SERVER to
    ... two nics - one nic is set to have the tcp/ip and filesharing - its used for ... Both will listen to rdp requests... ... dl380 server to isolate traffic and improve performance. ... We already have VLANS ...
    (microsoft.public.windows.terminal_services)
  • Re: Does this sound like a bad nic?
    ... Can you please provide some more information about your setup and how you're using VPN and RDP? ... When you are at a client PC and are unable to connect to the SBS using RDP, can you ping the server, see shares, and otherwise access server resources as expected? ... I first delete/recreate the TS connection. ... Setting it back to "all" nics does not resolve it until I have ...
    (microsoft.public.windows.server.sbs)
  • Re: Netlogon Error Causes RDC to Fail Until After Local Logon?
    ... gone to the server and logged on locally. ... NICs.) ... reboot for this month is already used up. ... The ability to use RDP to get to the server ...
    (microsoft.public.windows.server.active_directory)
  • Re: [fw-wiz] separating the servers on a switch
    ... > We want to control which server can talk to which other server (in the ... > segment), utilizing one of the firewalls. ... layer 2 connection. ... Static ARP tables: ARP only the routers/firewalls and the devices each ...
    (Firewall-Wizards)