Requires Free Membership to View
To further diagnose this problem, I'd use a LAN analyzer to capture traffic on both the wireless and wired links. By comparing traffic on both sides of the AP, you can see whether some traffic is being blocked. You may also be able to see error messages carried in NetBIOS traffic if packets are not being blocked but rejected by your Windows 2000 server. Use nbtstat and net commands on your wireless station to easily generate NetBIOS when capturing traffic.
Member feedback:
I am neither using VLAN, nor am I filtering any protocols. A suggestion was made that maybe the built-in network card on the server was the problem and that I should try installing a separate card and using that one. I don't see how the card can allow some network traffic and not other traffic coming from a wireless access point that is hard wired to the network. Do you?
Lisa's response:
No, I don't think the server's network card is likely to be the problem, since arriving traffic in both cases is carried by standard 802.3 Ethernet, and your existing server hardware worked fine until a few months ago. If you've ruled out the access point's configuration as the culprit, you should suspect the server's network settings, starting with a detailed comparison of packets captured during both successful and unsuccessful NetBIOS requests.
This was first published in July 2004
Network Management Strategies for the CIO

Join the conversationComment
Share
Comments
Results
Contribute to the conversation