Windows networking only become challenging when you need to extend Microsoft NetBIOS protocols to other subnets...
-- for example, port-forwarding NetBIOS through a wireless router, or enabling Windows domain browsing through a VPN gateway. As long as you're talking about a single physical LAN or a VLAN, NetBIOS broadcasts (like name announcements) will be received by all other stations (both wired or wireless) in that broadcast domain.
In your case, you already have a Win2000 network set up for your small business. You could install an AP on the same Ethernet as your Windows Server(s), and directly connect Win2000 Pro Clients to that AP. In this configuration, I strongly recommend enabling WPA-Enterprise on your AP, using your Win2000 Server to support 802.1X authentication. Microsoft provides documentation for deploying 802.1X using MS IAS, or you opt for an 802.1X small business solution like LucidLink. After a wireless client authenticates with 802.1X, it will have exactly the same access to your LAN as any other wired client, including access to file and printer shares.
Related Q&A from Lisa Phifer
The enterprise mobility management market for wearable devices is in its infancy, but IT can still use existing EMM tools to manage wearables.continue reading
Wireless expert Lisa A. Phifer explains to what extent WEP cracking remains a worrisome issue. It all depends on your company's WLAN security policy.continue reading
Wireless expert Lisa A. Phifer explains why you shouldn't stop using 802.1X authentication methods for enterprise WLAN access control.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.