Wireless 802.1x netwrok and Untrusted Root Cretificate?

Folks,
My college uses a secure 802.1x wireless network that I've been trying to join my AppleTV to (latest software) . Unfortunetly, our IT folks are using a self-issued root certificate that is then "trusted" in Active Directory using policies - it doesn't seem to work with the AppleTV. Can anyone tell me am I out of luck here?
Thanks,
Michael Lynch

Hi,
I believe the issue is more related to the internal clock not set to validate the certificate. The AppleTV does not keep its time and relies on the internet to update its clock. One of the only ways to update the clock using 802.1x is to plug in an ethernet cable to update the clock then removing it and the 802.1x Wi-Fi profile should take over if configured correctly. I too use an "untrusted" certificate and it does work following the ethernet cable work around, however, the moment you power it off, you will not be able to connect until you go through the steps again.

Similar Messages

  • [SOLVED] Wireless 802.1x PEAP Windows 7 and Windows 2012 NPS and CA

    Hello,
    We are in progress of migrating our RADIUS (Windows 2003 R2) and Certificate (Windows 2003 R2) servers to 2012 (R2). This went fine, no problems. After that we have changed
    our Wireless controller a Cisco 5508. We have change our certificate from a 1024bits to a 2048bits certificate.
    We tested the other certificate functions and that went fine too.
    But we experience a problem with wireless 802.1x in combination with Windows 7 machines. We have Windows 8 and 8.1 machines that do not experience this problem and wireless 802.1x?
    We recreated the wireless policy but also no success.
    We have seen this problem before, with a customer who had a Windows 2008 R2 certificate server and Windows XP machines with wireless 802.1x . Exact the same problem. After
    decommissioning the Windows 2008 R2 certificate server and changed it to a Windows 2003 R2 certificate server, there where no problems any more.
    It looks like that older versions of Windows do not work with newer certificate servers?
    Do we miss something? Can someone confirm this.
    We already looked for these forum posts, but with no success
    http://social.technet.microsoft.com/Forums/windows/en-US/796d447f-518c-4ccb-81ff-921ee561d742/win2k8r2-peapnps-with-cisco-wireless-controller-problem?forum=winserverNIS
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/76644dcc-911d-451e-b7f1-39269db43ac7/nps-event-6273-reason-code-16
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/d543fe75-0cf9-49e7-bbfa-dd0df219cfe5/the-radius-request-did-not-match-any-configured-connection-request-policy-crp
    Network Policy Server denied access to a user.
    Contact the Network Policy Server administrator for more information.
    User:
    Security ID:                            
    domainname\NB80W7$
    Account Name:          
    host/NB80W7.domainname.local
    Account Domain:                               
    domainname
    Fully Qualified Account Name: domainname\NB80W7$
    Client Machine:
    Security ID:                            
    NULL SID
    Account Name:                                  
    Fully Qualified Account Name: -
    OS-Version:                            
    Called Station Identifier:                    
    08-d0-9f-ec-96-60:domain
    Calling Station Identifier:                   
    a0-88-b4-35-2e-08
    NAS:
    NAS IPv4 Address:                 
    192.168.2.6
    NAS IPv6 Address:                 
    NAS Identifier:                       
    WLC5500
    NAS Port-Type:                                  
    Wireless - IEEE 802.11
    NAS Port:                               
    1
    RADIUS Client:
    Client Friendly Name:             
    WLC5500
    Client IP Address:                              
    192.168.2.6
    Authentication Details:
    Connection Request Policy Name:     
    WLC5500
    Network Policy Name:            
    Authentication Provider:                    
    Windows
    Authentication Server:                       
    DC01.domainname.local
    Authentication Type:              
    EAP
    EAP Type:                               
    Account Session Identifier:               
    Logging Results:                                
    Accounting information was written to the local log file.
    Reason Code:                        
    48
    Reason:                                             
    The connection request did not match any configured network policy.
    Network Policy Server denied access to a user.
    Contact the Network Policy Server administrator for more information.
    User:
    Security ID:                            
    domainname\Username
    Account Name:                                  
    domainname\Username
    Account Domain:                               
    domainname
    Fully Qualified Account Name: domainname.local/ICT Specialisten/Username
    Client Machine:
    Security ID:                            
    NULL SID
    Account Name:                                  
    Fully Qualified Account Name: -
    OS-Version:                            
    Called Station Identifier:                    
    08-d0-9f-ec-96-60:domain
    Calling Station Identifier:                   
    a0-88-b4-35-2e-08
    NAS:
    NAS IPv4 Address:                 
    192.168.2.6
    NAS IPv6 Address:                 
    NAS Identifier:                       
    WLC5500
    NAS Port-Type:                                  
    Wireless - IEEE 802.11
    NAS Port:                               
    1
    RADIUS Client:
    Client Friendly Name:             
    WLC5500
    Client IP Address:                              
    192.168.2.6
    Authentication Details:
    Connection Request Policy Name:     
    WLC5500
    Network Policy Name:            
    WLC5500
    Authentication Provider:                    
    Windows
    Authentication Server:                       
    DC01.domainname.local
    Authentication Type:              
    PEAP
    EAP Type:                               
    Account Session Identifier:               
    Logging Results:                                
    Accounting information was written to the local log file.
    Reason Code:                        
    16
    Reason:                                             
    Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.

    Hi,
    Please confirm the Win7 clients has renew the certificate and deleted the old certificate. And confirm you are not using the default server certificate template.
    More information:
    Renew a Certificate
    http://technet.microsoft.com/en-us/library/cc730605.aspx
    NPS Server Certificate: Configure the Template and Autoenrollment
    http://msdn.microsoft.com/en-us/library/cc754198.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Slow wireless connection 802.11n AEBS and Intel Core 2 Duo MacBook Pro

    I have three Macs all currently connected wirelessly to the new 802.11n AEBS.
    Mac #1 - PowerMac G5
    Mac #2 - 17" MacBook Pro Intel Core Duo
    Mac #3 - 15" MacBook Pro Intel Core 2 Duo
    The wireless connection speed (when using the web browser) is fine for both Mac #1 and Mac #2 but noticable slower for Mac #3. All three Macs are sitting right next to each other. All three Mac are getting an excellent signal. All three Macs are running the same version of the OS. All three Macs have identical network setting (as far as I can tell).
    When connecting Mac #3 to the AEBS via an ethernet cable, performance is good. I've also tried configuring the channel manually in the AEBS to channel #1 but this did not help (seemed to help others in a different thread). Additionally, I ran the 802.11n enabler and performance was bad both before and after its installation.
    Any idea why the Intel Core 2 Duo MacBook Pro would be performing differently?

    Ok eveyone. I did some digging and was able to get the network speed back with my Core2Duo machine. I put the Airport Extreme into Bridged mode and connected the Ethernet cable to one of the LAN ports, not the WAN port. After that everything works great. for more information check out this lengthy thread...
    http://discussions.apple.com/thread.jspa?messageID=3989864&#3989864
    and this site mentioned...
    http://www.macintouch.com/reviews/airportn/#performance
    Apparently the new base stations have a few issues that need to be worked out so I'd consider this a workaround. There should be no reason to have to do this. Good luck.

  • AX and wireless 802.11g printer sharing

    Would anybody know to configure this:
    Situation:
    An existing AX connected to the internet and sharing it's internet access with two users - working fine
    Question:
    Is it possible to configure this network so that a coexisting wireless 802.11g printer can also be shared between the two users (wirelessly - not using the USB port on the AX), without the users having to alternate their Airport card between Internet-network and Printer-network?

    It is possible if the printer can be configured to wirelessly join the network provided by the AX.

  • Best way to extend wireless via airport express and time capsule

    best way to extend wireless via airport express and time capsule
    i live in a two storey house where i use my airport express to create a wireless network in the main floor, and time capsule to extend it in the upper floor, where my room is. i have like 16 mbps in the main floor, and 2-3 mbps in the upper floor after having speediest.
    i used time capsule in the upper floor because i use wireless backup daily and don't want to put internet down while i im doin it and consequently my parent can have internet access in the main floor, am i right? or do i have make just the opposite in order to have a good internet speed?
    secondly, while checking airport express wireless mode on airport utility, there is like 4 different type of radio mode(802 11n bg comp, 802 11n 2.4, 802 11n a comp, 802 11n 5ghz) which i have no idea what they mean
    what do you recommend?
    we have like iphone4, iphone 3g, mbookpro, ipad, ipad 2, samsung tv and a sony vaio laptop in the wireless network
    thank you

    What you have would appear to be working but I can comment how I would redefine your setup.  Note that both Airport Express and Time Capsule can function as wireless base stations so you do have wireless everywhere and at all times — using the Time Capsules for backups doesn’t mean your parents won’t have internet access regardless of the where the base stations are located.
    You appear to have devices to connect to your network that use the 2.4 GHz band with 802.11g such as the iPhone 3G and perhaps the 5 GHz band with 802.11n such as likely the Macbook Pro if it’s a recent model.  The iPhone 4 can use 5 GHz and 802.11n.  Can’t comment on the Sony and Samsung but you can check their specs.
    Now the Time Capsule (if it’s a recent version), can simultaneously supply 2.4 GHz and 5 GHz band signals, but the Airport Express (if it’s recent) can only use one of those bands at one time.  Likely the lowest common denominator for your devices is going to be the 2.4 GHz band since the devices that are capable of using 5 GHZ also support 2.4 GHz.  If you don’t use 5 GHz, you won’t lose much in a two-storey home because likely it’s the 2.4 GHz band is better signal anyway because 5 GHz signals drop off quickly with several walls/floors to penetrate.
    You also didn’t mention if the Airport Express is used to support a printer and/or AirPlay (using iTunes to play on remote speakers via the Airport Express connection) but that might also be a factor in the best location to place the Airport Express.  Although the printer could be switched between the Time Capsule and the Airport Express if needed, only the Airport Express will support your remote speakers.
    Recommend you use the Time Capsule as the Base station.  When using Airport Utility to define the network, after you name your network, etc., select the Wireless tab, check the box “Allow this network to be extended” and set the Radio Mode to "802.11n (802.11b/g compatible)”.
    Using the Airport Utility, click on the Airport Express; after you define the device and network name, select the Wireless tab, define the Wireless Mode as “Extend a Wireless Network” and check the box “Allow wireless clients”. 
    Hope that helps.

  • Photosmart C7250 wireless 802.11b fails

    My new C7250 works well with USB and wired ethernet, but fails miserably (prints slowly, if at all) on my wireless 802.11b network.  All other devices work well on my wireless network.  I've spent many hours with HP and exhausted their first line support.  They supposedly have opened a case but I have heard nothing in a week.  Meanwhile, I took a network trace using WireShark and it shows a large number of retransmissions.  (I'm expert with application/network performance profiling.)  All you have to do is browse to http://192.168.1.xxx/ to test transmission -- don't even need to install drivers or printers to see the errors.  This problem appears to be with wireless support on the C7250.
    Has anyone experienced problems or success with 802.11b on this device?  How about 802.11g?  I would be willing to upgrade my wireless if I knew that it would resolve the problem.
    What does it take to escalate a probem with HP for resolution?

    All 2004 and newer wireless HP Inkjet printers are compatible with 802.11g and 802.11b networks (otherwise we couldn't get 802.11g Wi-Fi certification).  Besides testing for interoperability, we test for a minimum wireless throughput at the TCP layer.
    I'd like to see the internal connectivity report that you can generate by pressing the <setup> and <#> buttons simultaneously.  Scan the report to a memory card, copy it to your PC and post the image here.
    It will tell me information about your wireless network and other networks in the area.
    I have a couple of other questions:
    Does the slow printing go away after a power cycling the printer and then does it return later?
    Does the slow printing go away after a power cycling the wireless-router and then does it return later?
    Are you seeing retransmissions of TCP, 802.3 (ethernet) frames or 802.11 frames?  I wasn't sure at what layer you are sniffing the data at?
    What make and model 802.11b wireless-router are you using?
    Do you have encryption enabled?  Does disabling encryption change the speed of printing?
    How many wireless PC's (Macs?) to you have on your network?  Do they all exhibit slow printing?
    Have you changed the default fragmentation settings of your wireless-router?
    At home, I routinely get 1.5 Mbytes/sec transfer rates between my 802.11g wireless-routers and my HP printers and about 700 Kbytes/sec in 802.11b mode.
    One other thing you can try is to go to the printers internal web page, browse over to the Networking, Wireless, Advanced page and enable the configuration "In an infrastructure network use 802.11b behavior".
    Regards / Jim B
    Regards / Jim B / Wireless Enthusiasts
    ( While I'm an embedded wireless systems engineer at work, on this forum I do not represent my former employer, Hewlett-Packard, or my current employer, Microsoft )
    + Click the White Kudos star on the left as a way to say "thank you" for helpful posts.

  • In Snow Leopard, is there a way to import a wireless 802.1x System Profile via Terminal?  If so how?

    I am trying to deploy a Snow Leopard image via Casper running on a Lion server.  Everything works fine but I'd like to be able to have the image include a wireless 802.1x system profile without having to do it manually post.  I had it as part of my base image but for whatever reason it breaks during the process so I'd like to be able to create a task sequence to deploy it during the image process.  What's the best way to do this?  Thanks in advance!

    Hey SchenkerBob,
    It is possible to disable non-system fonts temporarily for all applications using the Font Book application. This article explains how to do so -
    Mac Basics: Font Book - Apple Support
    In particular -
    Disable and enable specific fonts
    In situations where you'd like to prevent a font from being available in applications, but you don't want to completely remove the font from your Mac, you can use Font Book to disable the font.
    In Font Book, click "All Fonts" in the Collection column.
    Click the name of the font in the Font column.
    Choose Disable "Font Name" Family from the Edit menu.
    Since it might be problematic to have to disable each font individually, you can create a collection of fonts and disable the collection. See the article for how to create a font collection -
    Organize fonts as collections
    When working with fonts, you may discover that you use certain fonts frequently, but rarely use others. To make it easier to find the font you are looking for, you can organize your fonts into collections.
    From the Font Book File menu, choose New Collection.
    Type in a name for the new collection.
    Click "All Fonts" in the Collection column.
    Drag the fonts that you want from the Font column onto the name of your new collection in the Collection column.
    You can then disable collections of fonts -
    You can also disable or enable all fonts in a collection: Click the name of the collection in the Collection column, then choose Disable "Collection Name" or EnableCollection Name" " from the Edit menu. 
    Thanks for using Apple Support Communities.
    Happy computing,
    Brett L 

  • Wireless 802.1x with Window 7

    I have a WLC 6.0,  ACS 3.3 and the SSID is setup to use 802.1x with Peap Authentication.   The clients are using Windows 7 to connect to wireless.     To get the clients connected they have to go into there network properties if the wireless card,  configure the client to use PEAP,  uncheck validate server certificate, and also uncheck use computer name to login into windows.  This works fine and the user to able to connect to to wireless after dong all these steps and then entering in there Windows Username and Password.    The customer is saying that this is to many steps for the end user and they just want the user to to click on the SSID and connect.  If wireless could also be setup to use  there windows username and password   would be a bonus.  I'm basically looking for a solution that is simple but is also secure as well.  I know that's an oxymoron.   Is there anything I could do to make the wireless process simpler.  Either by going with a different security authentication or by doing something different on the clients computers.   Thanks for any help and suggestions. 

    This is a script that we use on our campus (University of Leeds), that self configures an 802.1x connection and when a user connects to an 802.1x connection merely asks them for their username and password, which then remained cached.
    The .exe you create takes away all the techy bits that do 'confuse' some users, even if they are provided with well written documentation.
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}
    https://sourceforge.net/projects/su1x/
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}
    http://lsayregj.swan.ac.uk/su1x/SU1X_User_Guide-v104.pdf
    Features include:
    - Automation of configuration of a PEAP wireless connection on XP(SP3),Vita and Win 7
    - Can set EAP credentials without additional user interaction (avoids tooltip bubble)
    - Installation of a certificate (silent)
    - Checks for WPA2 compatibility and falls back to a WPA profile
    - Third party supplicant check -SSID removal and priority setting
    - Support tab: (checks: adapter, wzc service, profile presence, IP)
    - Outputs check results to user with tooltip and/or to file
    - Printer tab to add/remove networked printer
    This tool is very cleverly written by Gareth Ayres at Swansea University

  • AEBS 802.11n, TC and APXn with 7.3.1 is very flaky indeed - cant connect -

    HI Guys I think many of you on these forums have posted because you are having joyless experiences with the new APX 802.11n, the AEBSn and the TC not able to be managed via the AIRPORT UTILITY.app v5.3.2 with firmware 7.3.1 in the former devices. After a search there's many of these posts with people with the same issues.
    I have these devices in my place so I have had lost of experience configuring these over the years:
    1 x 802.11n AEBS, 1 x TC, 1 xUFO white AEBS, 2 x APXg's and lastly the problematic 1 x APX802.11n (one subnet and 2 x networks 2.4Ghz and 5 Ghz)
    I am at my wits ends trying to get the new APXn regularly responding to the AP utility.app (error reading configuration).
    I have tried most of the remedies on these forums but they do not consistently solve the problems of the APX not responding to the AP utility.None of these have consistently worked:
    • trying to factory reset it using the POWER ON+RESET and waiting for the amber flashes then green - butt this procedure NEVER WORKS to factory reset!
    • using the reset button in any form (it doesn't do anything)
    • connection through ethernet (sometimes works ).
    • takes long to power up (than the older 802.11g)
    • rest APXn back to factory defaults through the AP utility then ...
    • downloaded 7.3 firmware - worse and wont work
    • lastly I found that RESET+POWER ON then wait for 20 secs as as it powers up DEPRESS the RESET again and then it becomes readable.
    Additionally, I have been unsuccessful in getting PORT FORWARDINg to work at all for the AEBS 802.11n with and without the TC in the mix. I had this working for several years with the White UFO AEBS ... It beats me.
    I think the firmware is very very flaky and i have no resolutions for these recent problems.
    Hope for a fix soon.
    I will be polling these forums for any clues.
    w

    Hi Guys
    REgarding the APXn's (802.11N Airport express) inability to consistently be seen by the Airport Utility.
    this just worked finally for me now and have tested this 7 times and all seems ok now..
    Simply: when APXN in list, save configs, reset to factordeafuts, downgrade to 7.3, upgrade to 7.3 and reinstate .configs.
    UPdate: a probable work instruction that seems to consistently work.
    Here is the work instruction i used.
    (1) turn off all other WIFI base stations where you are that you can. (important I believe)
    (2) turn off airport in your mac
    (3) connect troublesome APXN to mac via ETHERNET cable. Set DHCP on your mac or some address in IPV4
    (4) power off and on the APXn  (yes again )
    (5) whilst it is powering up, use a pen of toothpick to RESET the APXn again (i think this causes something to move around inside the magic-ware)
    (6) the light will flash amber (no network to connect to)
    (7) launch /utilities/airport utility.app
    (8) the one and only APXn appears in the list
    (8.5) optional: (cross fingers and legs :))
    (9) when profile comes back, use FILE/SAVE a COPY AS to the ~/desktop to save the complete profiles and settings of what you have in there currently.
    (10) select the one and only APXn and perform a airport utility.app/base station/ RESET TO FACTORY DEFAULTS - and wait for 30 secs and then it will restart
    (11) when complete, quit and relaunch the /utilities/airport utility.app
    (12) the APXN will be as when you bought it (pristine and no stuff in it from you)
    (13) connect your mac back to internet via ethernet if possible. (avoid the wireless just to be sure but at this stage you could reinstate all your exiting wireless infrastructure)
    (14) select the one and only APXn AGAIN and perform a airport utility/base station/ UPLOAD FIRMWARE and select version 7.3 (back level) . THe firmware will load into APXn 0%-100% guage and then it will restart.
    (15) when complete, quit and relaunch the /utilities/airport utility.app and it will warn that one of the basestations (the only on the list - the APXN) has later FIRMWARE available for it. [This is 7.3.1].
    (16) reply OK to UPLOAD NEW 7.3.1 firmware. (yes yes I realise ths sounds silly but it works ok ) 7.3.1 Firmware will up load into the APXN as above and restart will take place.. so say 120 seconds.
    (17) quit and relaunch the /utilities/airport utility.app. THE APXN will appear as before as now with 7.3.1.
    (18) just to make sure, (we're not quite finished), remove the ETHERNET cable. If not already done form previous optional step, ENABLE the AIRPORT (WIFI) on your mac.
    (19) power OFF then power ON the APXn.. wait for the usual 70 secs..
    (20) Again, to be sure, QUIT and RESTART the /utilities/airport utility.app, the APX as factory default with amber icon will appear in the list [along wit the rest of your apple airport base stations).
    (21) Select it in the list fo MANUAL and the configuration will be read quickly.
    (22) do this (steps 18-21) 3 or 4 times to see that it is consistent. (I this it 7 before posting this).
    last step...
    • select the APXN (default settings) and IMPORT the save configuration file (~/desktop/nnn.baseconfig) (all it) from the ~/desktop. Ignore any errors (untick them), add a password for the base station and UPDATE!
    • wait for the usual 70 secs.
    • without quitting the /utilities/airport utility.app, the UPDATED APXN with your configuration will be in the list.
    NOw try and selectit for manual and it should respond in time without timing out.
    Test by powering off and removing from wall socket and moving around too to make sure you can SEE it in the /utilities/airport utility.app and select it for MANUAL CONFIGURATION.
    After many days of frustration on weekend and over night, this appears to have worked ok for me.
    (now to work out the AEBSn port forwarding issue - it wont work).
    HTH
    w

  • HT4259 I have an 802.11n base and extender and still cannot get a good signal 80-90 ft away . Why?

    I have an 802.11n base and extender and still cannot get a good signal 80-90 ft away . Why?

    Hardwire is always recommended because there is virtually no signal loss in a wire....at least up to 300 feet or so.
    Another advantage of using Ethernet cable...if you can...is that you can locate the AirPort Express where it is most needed.
    If it extends using wireless only, it pretty much needs to be located about half the distance from the main router and the general area that needs more coverage.
    I like to use WiFi Explorer since it displays SNR (Signal to Noise) readings, which are the best way to evaluate signal quality.
    Mac App Store - WiFi Explorer
    If the signal is varying constantly, something is causing it to do so....assuming that the AirPorts are functioning correctly.
    Cordless phones are a huge problem for wireless networks.  You want to try to figure out if the phones are causing a problem as a first troubleshooting step.
    That is why I suggested that you turn off the phones for an hour or two and watch the network to see how it behaves.  If the signal stops fluctuating....that is a good clue that the phones are interfering with the wireless signal.

  • Network Design - Root and Non root bridges

    Hi,
    We have a network set-up as the below image. Where the switches have STP enable to handle the muliple paths for the data to flow.
    What I would like to know is should the 2 bridges plugged into the same switch e.g Switch A (Bridge A and Bridge B) both be root bridges and (Bridge C and Bridge D) both be non root.
    Or should for example, Bridge A be a root and Bridge C a non root and Bridge B a non root and Bridge D the root?
    Similarly with the rest of the other bridges E, F, G and H
    Thanks

    Disclaimer
    The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.
    Liability Disclaimer
    In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.
    Posting
    Ah, I think I understand.  So the wireless bridges are "transparent" to the rest of the network.  They just convert wired to wireless and back again.
    If I have that right, we can ignore them and just consider your switches.
    In that case, it appears you have two L2 loops, those formed by the dual paths between switches A and B and between switches C and D.  From a topology standpoint, it doesn't seem to matter what switch you select as root and secondary root.  However, as switches B and C are the interior switches, I would suggest those as your root and secondary root switches.

  • Where to download the "Windows 2000 Wireless 802.1X hot fix"?

    From the "Cisco Aironet Wireless LAN Client Adapters Configuration Guide for Windows", it indicates that Windows 2000 can support host-based EAP with the "Service Pack 3 or greater and the Windows 2000 Wireless 802.1X hot fix".
    However, I cannot find the 802.1x hot fix in Microsoft. Please kindly advise how I can download this hot fix. And, what is the function of this 802.1 hot fix?
    Thanks!!!!

    Hi!
    Here you have the link to the hotfix :
    http://www.microsoft.com/downloads/release.asp?ReleaseID=45017&area=search&ordinal=1
    Regards
    Fredric

  • Root-Bridge and Non-Root Bridge Support

    I was wondering if the ISR Routers (Cisco 1811w) support the root-bridge and non-root-bridge feature. If not is there another device apart from the 1310 and 1410 bridges that support this feature?
    Thank You,
    VT

    Hi VT,
    The ISR AP supports both of these roles;
    Access Point Link Role Flexibility
    Access Point Link Role Flexibility allows access point radios to operate in a combination of radio roles,
    such as access point root, bridge root (with or without clients), bridge nonroot (with or without clients).
    This provides a more flexible deployment scheme to support the various applications requirement. Note
    that the ISR AP does not support access point repeater and WGB.
    Wireless Non-Root Bridge
    The wireless non-root bridge allows the access point radio to operate as the remote node in a point to
    point or point to multi-point network.
    Wireless Root Bridge
    The wireless root bridge role provides support for both point-to-point or point to multi-point bridging.
    http://www.cisco.com/en/US/docs/ios/12_4/12_4x/release/notes/rn1800xj.html
    Hope this helps!
    Rob

  • Broadcom Wireless 802.11n low Mbs speed

    Hello All,
    I just picked up a refurbished G500 and overall I'm pretty happy with it...with one major exception. The #1 criteria when I was laptop shopping was that it provided 802.11n support (my old laptop was just 'g').
    Anyway, long story short, I am not experiencing any connectivity issues however I'm lucky if I connect at anything above 55 Mb/s. I switched over to my 802.11g router and my connection speed dropped down to 5 mb/s... so there is obviously an issue.
    All suggestions are welcome, but let me rule out the typical initial responses:
    * I have a Dell laptop that connects to my 802.11n router at 150Mbs so I know the router is fine
    * I have tried the generic Windows Broadcom Driver
    * I have tried the Lenovo Broadcom Driver for Win 7
    * I have tried the Lenovo Broadcom Driver for Win 8
    * I have tried the Lenovo Broadcom Driver for Win 8.1
    Also note that I'm in I.T. but wireless isn't my strong point. When I first got the G500 before I did anything to it (so OEM image) the wireless connected low (Think the highest I saw it was 72 Mbs at one point).
    I have since wiped that laptop and installed my own copy of Win 8 Pro (and then Win 8.1 Pro Update) and still getting the same speed.
    So I feel like I have pretty much ruled out any OS issues (since I've been on 3 at this point). Drivers are always a possibility but I've tried everyone out there. And of course Hardware would be my last thought although it works.. just not that fast.
    I'm also wondering:
     * Is this card (Broadcom vendor Device ID 4727) even able to connect at that speed.
    *  Is the G500 wired with the required antenna's to get even 150 Mbs. From my understanding you must have 2 in and 1 out to get 150 but I could be wrong.
    Oh, and as a last resort, would just replacing the stock WLAN with a better aftermarket be an option? 

    I have same problem with you when first use Broadcom 11n wireless card (only got constant 39Mbps). But I've fixed by changed wireless channel in wireless router to less intensity channel (1 or 2...) and set Broadcom driver option "Bandwidth Capability" to "11b/g:20/40Mhz". After that I can get wireless speed from 135 Mbps to 150Mbps.

  • Problems connecting on Wireless 802.11n with my T61 with Intel Wireless AGN

    Hi, I live in Thailand and have a similar problem as others with my Intel Wireless AGN connection as others.  I have a D-Link Model DSL-2740B Rangebooster N ADSL2/2+ Modem Router. It is supposed to support 802.11n draft wireless connections of up to a maximum of 270 MBPS versus 54 MBPS for 802-11G wireless. Of course, I don't expect it to reach the maximum transfer speed, particularly here in Thaiand, however I would expect it to produce results better than the 54 MBPS rate for 802-11G. I first tried it on my ThinkPad T61 which incorporates Intel® Wireless WiFi Link 4965AGN. When connected, it shows a speed of 54MBPS (802-11G) instead of higher wireless 802-11n speeds. I've upgraded my router to the latest firmware and have tried different configurations with no improvement in performance. One think I have noted is that when I make an on-line configuration change to my router configuration then select "apply", immediately my ThinkPad rate changes to 150 MBPS momentarily then my connection is lost (to be expected as the router changes are being implemented), followed by reconnection of wireless signal only to return at 54 MBPS again. I also have an older ThinkPad model without built-in wireless capability so I purchased a Belkin wireless 802.11n USB adapter to connect to my router. Again, the maximum connection is at 54 MBPS. When I repeat configuration changes to my router as I did above, my ThinkPad connection momentarily changes to only 1 MBPS instead of 150 MBPS as in my other T61 ThinkPad then reverts back to 54 MBPS once the configuration changes have been completed. Has anyone successfully used wireless 802.11n successfully at the higher transfer rates (above 54 MBPS)? Is it possible that my TOT Goldcyber connection speed is artificially limited? I notice that my rated speed for my desktop computer connected to my same D-Link DSL-2740B only indicates a rated speed of 100 MBPS. I use Vista Home Premium 64-bit on my destop, Vista Home Premium 32-bit on my ThinkPad T61, but us Windows XP Professional on my older ThinkPad. I feel that my problem is either with my ADSL carrier (TOT) or compatibility with my D-Link DSL-2740B Modem Router and my ThinkPad T61 internal wireless card and/or Belkin wireless n USB adapter. IT-City is letting me swap out the Belkin USB for the D-Link Rangebooster n DWA-140 USB adapter next week when they restock. The only other think that I can think of is that wireless n just doesn't work in Thailand and that maybe I should just stick with wireless G and go with a higher powered wireless USB model such as the business rated EmGenius EUB 362 EXT. Has anyone used this model and had good success with it; I've heard that it is a long range model and has the capability of reaching 108 MBPS through some sort of magic? Looking forward to reading your replies and possible solution.
     Pattayadavid

    Hi!
    Intel Wi-Fi cards support full 802.11n speed of 300 Mb/s working at 5 GHz range only. Your D-Link DSL-2740B works only in 2.4 GHz range. So to get 300 Mb/s you have to get another wi-fi router that supports 802.11n in both 2.4 and 5 GHz, for instance Lynksys WRT610N or Apple Airport Extreme or whatever.

Maybe you are looking for