Domain and Wifi clients

By rlynch@lockhartcadillac. ·
Ive got a few areas in my company where getting cable to is extremely difficult, therefore we???ve always had them setup on wifi. Pretty much standard access point wap security with the client machines ranging from Linksys, dlink, intel wifi adapters. Ive recently deployed a domain controller for dns, dhcp, and software deployment purposes. My wifi clients really seem to have problems taking assigned software over gpo. I check to see if they had a ???slow??? connection and they did not. They will take all the other gpo???s, but software assignments just wont take. Do I need to setup my wifi in a different matter, or is wifi just hit and miss on a domain? I would really appreciate any help you can offer. I have done some research online but I figured I would also asks the experts out there that may have run into this before. Thanks.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

SMB and WiFi do not mix well

by robo_dev In reply to Domain and Wifi clients

While WiFi works very well for normal TCP/IP, it can be tricky to get Microsoft networking SMB protocols to play well on the WLAN.

There are at least a half dozen issues that can be problematic, such as:

a) WiFi connections lose packets, and Active Directory uses Kerberos over UDP for authentication. UDP has no mechanism for dealing with lost packets, and therefore authentication issues can happen unless you modify the client PC registry to force them to use TCP for kerberos.

b) SMB is broadcast-based, and some WiFI devices are configured to limit the rate of broadcast traffic by default. This can be configured on enterprise-class wifi gear such as Cisco.

Other broadcast-based services, such as DHCP and WINS, can be problematic on the WLAN, depending on the clients, the WLAN hardware, and how it's all configured.

A common problem on a WLAN is that there are often a wide variety of devices, so, for example, the TCP/IP stack in a Nintendo DS game console may act very differently than that of a HP wireless printer with respect to DHCP.

If you are using a consumer-grade WLAN Access Point device, it may be using a protocol such as uPNP (network Plug and Play) or even things like Appletalk.....the last things you want to see on a SMB network.

c) SMB does not play well across multiple subnets, so if there are WLAN routers versus Access Points, it's not going to work.

d) WiFi devices tend to be battery powered, thus they goto sleep. Certain services like DHCP and Wins get confused and confounded when the workstation goes off the network and comes back, such that there can be mixed up DNS cache, mixed up routing tables, etc, etc. So often you cannot use DHCP for WLAN devices, and may need to hard-code WINS and DNS settings.

Tell us more about specifically what clients you are using, and what WLAN gear you have deployed, that will give some ideas about where to start digging.

Related Discussions

Related Forums