Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to bridge some distance between a wired network and a wireless internet access point by setting up NAT using a wireless adapter - to that end I asked another question earlier.

However, I'm also considering another tack: getting a decent internal wireless adapter. Does anyone know of a wireless chipset that has solid, reliable drivers for 64-bit Windows Server 2008?

(I have some form of Atheros chipset currently in a Belkin USB wireless adapter, using a 64-bit Vista driver (athrxusb.sys ver., and have had about 6 bluescreens today that I would pin on the driver - it's the only non-MS software on the machine, and the machine was reliable with a different install previously.)

share|improve this question
up vote 2 down vote accepted

Finding a wireless device that natively supports server 2008 might be hard, but let me give you a solution.

What if you use a router like the Linksys WRT54GL with a firmware like Tomato. Now, the advantage of using this solution is that the router can be turned in to a Wireless client instead of a Access Point the 2nd router will act as the wireless adapter, then you can tell the Wireless Client(2nd router) to either assign a static IP or use DHCP for any device connected to it.

I've included a small image. alt text

I can't remember if the default Linksys firmware supports the Wireless Client feature.

Hopefully this all make sense.

share|improve this answer
Interesting idea. It may end up being the way to go, though I'd rather centralize all net access from the internal networks through a single machine, rather than a single router, not least because there is more than one network I'm trying to share net access to. But adding another network adapter dedicated to this router may work... – Barry Kelly Aug 15 '09 at 7:44
I've made an order for this part, and some other approaches. Thanks! – Barry Kelly Aug 16 '09 at 16:13

I'm happy to be told I'm wrong about this but wireless in a server, any server, makes my tummy feel funny - it feel 'wrong' to me somehow, there's almost always a better way of achieving your goal.

share|improve this answer
With respect, I've tried other solutions, which is why I've asked the specific questions I did. – Barry Kelly Aug 15 '09 at 7:36

Note that for many devices, the W7 drivers will work fine (and in some cases are identical) to the Server 2008 drivers.

Anyway, my suggestion to you is this:

Connect the wired NIC on the server to one of the ports on the back of the bridge, and the server won't know any better. Like another poster mentioned, this isn't exactly best practices, but sometimes you have to make due with what you're given :)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.