<div>
I guess the direction i was going was to save my ISP assigned addresses by creating a vlan and separate network and to setup a dhcp server just to cater to the clients. &nbsp;We only use their edge router and the ISP's addresses work in conjunction with their content filter setup and they charge for filtering based on the ips used.<br />
Thanx
</div>


I guess the direction i was going was to save my ISP assigned addresses by creating a vlan and separate network and to setup a dhcp server just to cater to the clients.  We only use their edge router and the ISP's addresses work in conjunction with their content filter setup and they charge for filtering based on the ips used.
Thanx

<div>
<div class="content wysiwyg-content">
We are pxe booting thin-clients to connect to a windows 2003 terminal server. &nbsp;Can i put in this tserver a second nic, set it to another subnet, setup DHCP on that subnet for the pxe booting and keep the thin-clients in a vlan (with appropriate switches) of their own? &nbsp;Would they still have internet through the original nic/subnet or would i need to setup routing in the server? &nbsp;There is also a network printer for the clients on there from another print server how would this affect it?<br />
thanks
</div>
</div>


We are pxe booting thin-clients to connect to a windows 2003 terminal server.  Can i put in this tserver a second nic, set it to another subnet, setup DHCP on that subnet for the pxe booting and keep the thin-clients in a vlan (with appropriate switches) of their own?  Would they still have internet through the original nic/subnet or would i need to setup routing in the server?  There is also a network printer for the clients on there from another print server how would this affect it?
thanks

thinclients in a vlan subnet

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.