Yes, it is most likely the LAN subnet on the radio that is causing the problem. 
 Microsoft made 169.254.x.x subnets non-routable beginning with Windows Vista 
operating system.  We had this problem about almost two years ago and once we 
finally figured it out, we just changed all of our radio LAN subnets from 
169.254.1.x  to 192.168.10.x subnet and it 100% solved this problem.

 

This problem only exists with firmware 9.5 or higher if memory serves me 
correctly, because I remember we initially rolled back firmware and it solved 
the issue “temporarily”, but the long-term fix was to change all the LAN 
subnets on the NAT’d radios.

 

I hope this helps.

 

Regards,

 

David Williamson
Owner

Custom Computers & Winchester Wireless

2979 Valley Avenue

Winchester, VA 22601

http://www.customcomputersva.com <http://www.customcomputersva.com> 

http://www.winchesterwireless.com <http://www.winchesterwireless.com> 

Work 1: 540.722.9688 x223

Work 2: 540-665-0800 x223

Toll Free Fax: 877-765-3700

[email protected] <mailto:[email protected]> 

[email protected] <mailto:[email protected]> 

 

From: [email protected] [mailto:[email protected]] On Behalf 
Of Scottie Arnett
Sent: Thursday, November 10, 2011 8:52 AM
To: WISPA General List
Subject: Re: [WISPA] Problem with Access to Canopy network

 

Are you doing DHCP with the client radios? If so, I remember some having 
problems if they used the 169.254.x.x private IP structure. Changing to another 
private structure solved the problem.

 

Scottie Arnett
President
Info-Ed, Inc.
Electronics and More
931-243-2101
[email protected]

        ----- Original Message ----- 

        From: [email protected] 

        To: WISPA General List <mailto:[email protected]>  

        Sent: Thursday, November 10, 2011 7:07 AM

        Subject: [WISPA] Problem with Access to Canopy network

         

        To All,

         

        I have a problem with about 15 users not able to access the net.  Their 
PC's network icon, lower right on quick launch toolbar - MS, has a yellow 
triangle w/!.  indicating that their ethernet interface has no access.  Each 
user has MS7.  

         

        This is specific to one tower location and three of the four sectors, 2 
Canopy 900's w/180* sectors, 2 Canopy 2.4's w/ 180* sectors.  At first we 
thought it was specific to MS7 Users, that is still the case.  However, not all 
MS7 users.  The setup of all CPE & AP devices is the same.

         

        We have reset one 900 to factory default and reconfig'd that device 
with no affect on the ability to access the net.

         

        Any suggestions, advice, questions or direction would be greatly 
appreciated.

         

        Ron Wallace

        Hahnron, Inc. (Tigernet Internet)

        [email protected]

        Phone:        517-547-8410

        Cel:            517-740-0941

         

________________________________

        
        
        
--------------------------------------------------------------------------------
        WISPA Wants You! Join today!
        http://signup.wispa.org/
        
--------------------------------------------------------------------------------
         
        WISPA Wireless List: [email protected]
        
        Subscribe/Unsubscribe:
        http://lists.wispa.org/mailman/listinfo/wireless
        
        Archives: http://lists.wispa.org/pipermail/wireless/


--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: [email protected]

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to