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.
Dig Deeper on Working With Servers and Desktops
Related Q&A from Lisa Phifer
Learn the difference between a site-to-site VPN and a remote-access VPN, as well as the protocols used for each one.continue reading
Need to send an email, check your flight's status or get ready for a presentation? You can do it all on your smartwatch, thanks to a slew of Apple ...continue reading
New and improved management features have made Android devices more suitable for enterprise use, and API and EMM tools can streamline the device ...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.