Link to home
Create AccountLog in
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Avatar of ofiwex
ofiwex🇪🇸

VLAN capability in Windows 2003 server
Hi,

We have several VLAN configured in a Fortigate firewall and all of them connected to a DELL switch which supports VLAN.  All of that is working properly.  What we want to do now is to connect just one server that have access to all VLAN's by connecting the network card to the switch and defining as trunking the switch port.  How can we provide VLAN capability to the server without using a router, i.e. by providing VLAN software capability?.  It is a Windows 2003 standard SP1 server.

Regards,

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of benhansonbenhanson

VLAN functionality is part of the Network card and it's driver.  Windows will allow for listening on multiple IP addresses, as you will need one IP address for each vlan.

Avatar of ofiwexofiwex🇪🇸

ASKER

Hi behanson,

But, where should I setup the VLAN ID?.  Windows doesn't show any box to introduce the VLAN ID.  I know I can setup several IP in the network card but this nertwork card is going to be attached to the port of the switch which which will be trunking port so it would be shared with all VLANs defined in the switch, so the network card must mark the packets with the VLAN ID.

Regards,

It would be in the hardware config of the NIC.  If you go to device manager, expand network cards, right click on the NIC and click properties, then look at the options for the NIC.  Each manufacturer has different options.

The VLAN tagging will affect the way packets from the server traverse your switch, but it won't affect the IP address encapsulated in each packet.  Clients won't be able to talk to a device in a different subnet unless you have a router, or static routes defined on each client.

Think about when you have a dumb switch with multiple machines plugged into it.  Traffic from one PC to another is not physically segregated, but if they are not configured on the same subnet in their IP configurations, they won't talk to each other.  Same thing will happen with a server on multiple VLANs.  It won't be physically restricted from communicating with other VLANs/subnets, but it just won't be able to from a routing perspective.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of ofiwexofiwex🇪🇸

ASKER

Hi,
Thankyou for the info.  I know how the VLAN works, and it sounds good about the NIC card to have the VLAN ID configuration, unafortunately my network card doesn't have such feature.  It is a good Broadcom NetXtreme Gbit NIC card in a DELL PowerEdge 2950 server.  I think it should be any software solution for this.

Regards,


ASKER CERTIFIED SOLUTION
Avatar of benhansonbenhanson

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account

Avatar of ofiwexofiwex🇪🇸

ASKER

There is an expert mode, thant's why I didn't see the options... You're right, using the NIC control suite I can setup the VLAN's.

Regards,
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).