QoS binding limited to IP address range and SSID on WLAN

Our VLAN id 2 is used only by a WLAN SSID
Defining a QoS profile as using VLAN id 2 did not work. No upper rate limitation worked
Only using the IP address range of the VLAN or the SSID appeared to work.
It does not appear consistent, when a VLAN id can be specified on a WLAN in the  Wireless Basic Setting Table
It is also inconsistent, that the proper SSIDs are not listed in the drop down box on the
Add / Edit Profile Binding Configuration page. They only appear as AP-1, AP-2 etc.

Has this been fixed under firmware 1.0.4.17? I cannot get this work with any type of Traffic Selector (IP/MAC/VLAN/DSCP/SSID).
Any suggestions are greatly appreciated. Thanks!

Similar Messages

  • Windows 2008 DHCP Server Address Range and Exclusion Range

    Hi ,
    I have a couple of Doubts regarding DHCp windows 2008  server
    1) The DHCP server  is given a static Ip in a network series eg(192.168.1.x)  starting Ip is 192.168.1.1 to 192.168.1.254  , 
    and if the range is from 192.168.1.10 to 1.250 , 
    Should the DHCP server be not given an Ip in the DHCP range specified ?
    ie  the DHCP server static IP should not be in the 192.168.1.10-192.168.1.250 , ( I have given as 192.168.20.5)
    Even though the Exclusion range can be specified , Just want to know if this is best practice.
    2) And next setting up the range , should we give the entire network address as range ( eg 192.168.1.1 to 192.168.1.254) and set exclusion range 
    or  take a particular series  (eg 192.168.10-100) 
    Please advise
    Thanks in Advance
    Regards
    Anand M

    Your DHCP server range should update automatically to the 192.168.0.x  subnet when you change your "Local IP address" to 192.168.0.1.   Be sure to use a computer that is wired to your router when you do this.  Also, be sure to click on "Save Settings", then wait (3 to 60 seconds) for the screen to refresh.  You will likely be disconnected from the router when you do this.  Do not worry about this.  Power down the router and your computer.
    Next, wait 30 seconds, then reboot router and computer.  Your Local IP address and the DHCP server range should now have the same subnet.

  • Limitation on source group with services using ip address range

    Hello,
    I have an interface on CSS which I regard as public and another interface I regard as private. On the private interface is a server farm with private ip addresses. Since the server admin guys insisted the servers need to access internet just for Windows Update, I made a source group to NAT the private addresses to public addresses to allow the servers to access internet.
    I defined services for use by the source group. Since keepalive is not important in this case, I set keepalive none to ,I hope so, save system resources.
    I have server 192.168.1.1-5 (5 servers) and 192.168.1.11-14 (4 servers), so I made a service with ip address 192.168.1.1 range 5 and another service 192.168.1.11 range 4.
    But then I found that the two services cannot be put in the same source group. It is because of the different range in the service definition.
    I can get it work if I define services with single ip address, but then I will have a long configuration with repetative information. And I think this may be using more system resources.
    I can also get it work if I include 192.168.11.15 and define two services both with a range of 5 ip addresses. But 192.168.11.15 is not actually there.
    Why is there such a limitation on source group, or services with ip address range? Is there the same limitation for content rules? Or am I getting it all wrong and should do the configuration in other ways?
    Advices will be welcomed.
    CT Yau
    Hong Kong

    Yes you are correct. There is a limitation while adding services into source groups.
    You can create as many services that share an ip range (eg. a /24 subnet range). But the trouble starts when you add them into source groups. You can not add them into a source group NOR you can add them under different source groups as well.
    You mentioned that you can use single ip adress instead of range for the services...but it is not true as you will be stuck when you add them into source groups.
    I can think of these following options in your case.
    Option 1
    Change the ip range on the servers. Use 2 different IP ranges one for those 5 servers and another for those 4 servers.
    Create 2 services for each range.
    Create 2 groups and add the services.
    service server-out-192.168.1.1-5
    ip address 192.168.1.1 range 5
    active
    service server-out-172.168.1.11-14
    ip address 192.168.1.11 range 4
    active
    group server-out-192.168.1.11-14
    vip address x.x.x.1
    add server-out-192.168.1.1-5
    active
    group server-out-172.168.1.11-14
    vip address x.x.x.2
    add server-out-172.168.1.11-14
    active
    Option 2
    Create a service that includes all the ip addresses starting from 192.168.1.1 through .14 using the range keyword.
    Now you need to create one source group with a VIP. Add the service to the source group.
    If you do not want to cover the unassigned ip addresses just move them up and use consecutive ones.
    service server-out-192.168.1.1-14
    ip address 192.168.1.1 range 14
    active
    group server-out-192.168.1.11-14
    vip address x.x.x.x
    add service server-out-192.168.1.1-14
    active
    thanks

  • RV325 DHCP static address list and duplicates in unknown IP & MAC Binding List Table

    DHCP Manual Bindings are entered and are displayed correctly in the IP & MAC Binding Table.
    The error is that there are duplications of the IP address in the Unknown MAC Address List and hitting the Refresh button does nothing.
    These duplicates remain in the Unknown table forever. Only a reboot of the router really refreshes the Unknown table.
    Any suggestion?

    The problem has been solved.
    All the settings are apparently stored in the open directory database.  I had to enable system records and viola there was the extra entry complete with MAC address and IP address.

  • SBS 2011 - Need to change Machine name and IP address range

    We had upgraded to SBS 2011 and new hardware 6 months ago, we have recently been aquired by a larger company and want us to comply with their machine naming conventions and change the IP address range to fit in with their corporate structure.  They
    will be supplying us with a 2011/2012 Domain controller, this is to be added to our existing network as the primary DC supplying DNS, DHCP, WSUS
    We use our SBS box for DNS, DHCP, Exchange, File server, Print server
    How difficult is this going to be?  Is it actually possible, or do we need to wipe the SBS box and install from scratch?Any help on this matter would be appreciated

    As said, you can't change the name of the server or the domain, but you can change the IP addresses.
    The bad news is that you can't integrate SBS to a larger corporate network. SBS needs to be at the root domain of the forest and hold all FSMO roles, and it can't have any trusts.
    If the corporate wants to bring in a DC of their own AD domain and wants all clients to be joined to that domain, you just can't use SBS anymore, it won't fit in. You need to inform your corporate IT about the situation, and you need to make a new plan.
    You will need some kind of migration from SBS to standard products first before you can join to the corporate network structure.
    Tero Leskinen - MVP (Windows Server for Small and Medium Business / SBS)

  • Customer listing with address data and credit limits

    Hello all,
    I need a report I can download to Excel detailing address data and credit limits by customer.
    Many thanks.

    Hi
    You can not get the report with address details from standard reports. You have to download the address from table level to excel and you can do what ever you want. If you want a special report what you want you have to contact your programmer (ABAP).

  • Microsoft Exchange Categories in iCal, Address Book and Mail

    I work in a Microsoft environment with my MacBook Pro and would like to use iCal, Address Book and Mail as my default applications rather than Microsoft Oulook 2011, however, there is not support for the Microsoft Exchange Categories to be replicated into the various Apple applications. This results in my address book not to differentiate any longer from my contact categories stored on the Exchange server, nor my calendar. Categories can be created in iCal and other Apple applications but it then requires for the event or contact to be duplication "On my Mac" which makes me loose my synchronization with other systems. Any idea about to fix that?

    Same issue here. I would love to migrate to iCal but the lack of support for categories is a limiting factor. Same applies to Contacts.

  • Address Book and Mail - Using Groups for e-mail

    I've noticed something strange about Mail and Address Book in Tiger:
    I created a new Group in Address Book. The Group contains people who are involved in a project. I have names, home addresses and phone numbers for eveyone, but a few people do not have e-mail. When a try using this Group to send out an e-mail message, Mail warns me that John Smith does not appear to have a valid e-mail address. I can't send the message unless I select only those in the group who have e-mail addresses and only send to them. This is a pain.
    Am I doing something wrong, or is this a bug in Tiger's Address Book and Mail.app? How can I get around this? I have several Groups like this that contain entries with no e-mail.

    It's not a bug in Address Book, it's a limitation. Your only way to get around that is to either remove those from the group, or give them all the same email address; i.e., send those to you so you are reminded that they didn't get the email and you have to notify them some other way.
    And of course, when sending to more than one person, never put the recipients in the To or CC field; they should always go in the BCC field.
    Mulder

  • Offline Address Book and GAL corrupted.

    I have and Exchange 2013 cluster with 3 servers all performing both CAS and MB roles. This environment was originally a 2003 server, then 2007, then 2010, and now 2013 so it has been migrated many times in the past. It seems at some point something was missed
    and now we are having serious issues.
    It started when I was unable to create new profiles in Outlook. After much troubleshooting and digging I found I was also having a problem creating new mailboxes in Exchange and even updating settings such as mailbox limits. When I try to create a new Mailbox
    I receive the error:
    The LdapRecipientFilter "(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))(objectCategory=group)(objectCategory=publicFolder)(objectCategory=msExchDynamicDistributionList)
    ))" on Address List or Email Address Policy "\Default Global Address List" is invalid. Additional information: The attribute type 'mailnickname' or its syntax is not defined in the schema.
    This all seems to come down to issues with the Global AddressList and the Offline Address List. Thanks to other posts and Google I found that I should simply update these list using Get-AddressList | Update-AddressList and Get-GlobalAddressList | Update-GlobalAddressList.
    These commands however through some erros:
    Get-AddressList | Update-AddressList
    WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
    \/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
    group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
    administrative group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
    \/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
    group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
    administrative group" is invalid and couldn't be updated.
    [PS] C:\Windows\system32>Get-GlobalAddressList | Update-GlobalAddressList
    WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
    \/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
    group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
    administrative group" is invalid and couldn't be updated.
    Get-AddressList | Update-AddressList
    WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
    \/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
    group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
    administrative group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
    \/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
    group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
    administrative group" is invalid and couldn't be updated.
    [PS] C:\Windows\system32>Get-GlobalAddressList | Update-GlobalAddressList
    WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
    Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
    updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
    \/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
    group" is invalid and couldn't be updated.
    WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
    administrative group" is invalid and couldn't be updated.
    From what I read this is due to invalid characters in these entries of the Address Books. If I still had my 2010 box I could go in to the Exchange Toolbox, manage the Address Lists and change the Alias of these entries. I don't have a 2010 box though. All
    I have is 2013 and from what I have read there is no way to manage the Address lists through the ECP.
    I have tried changing them in the Shell with this command:
    Get-Mailbox | Where {$_.Alias -like "* *"} | ForEach-Object {Set-Mailbox $_.Name -Alias:($_.Al
    as -Replace " ","")}
    But this did not work.
    How do I fix this issue in an Exchange 2013 environment? Please let me know if more information is needed and thank you in advance for any help.

    Hi,
    I suggest we rebuild the GAL by contacting a Microsoft Support, or it will be a non-support environment. For your reference, a simple version of the rebuilding steps:
    1. Remove the current GAL
    2. Run “/PrepareAD” and it will recreate the GAL.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Yoga 13 Wireless Fix - far better range and speed using 5G Linksys AE6000 .11ac usb nub

    $60 Linksys model AE6000 802.11ac USB hub has made my Yoga 13 a useful device.  Benefits are as follows, along with a quick "how to" tutorial.  
    Far better range from my access point (80 feet with reasonable speed on Linksys vs. 30 feet using built-in Realtek WLAN card.
    Significantly faster speed 55 meg/sec using 5G, compared to stock Yoga/Realtek's 2.4 GHz-limited 14-16 meg/second download speeds - both tests done same day using Ookla Speedtest.net)
    No longer crashing after resume (I suspect the crashing that began with Win 8.1 is due to driver issue)
    Recognizes both 2.4 GHz and 5 GHz WLAN networks (Windows 8.1 failed to recognize 5GHz signal until I backdated the Linksys WLAN driver to use Windows 7 driver).
    TUTORIAL / STEPS:
    Turn off (or at a minimum - review before downloating) windows updates - otherwise Win8.1/Yoga will over-write the good driver you're about to install and revert you back to slow WLAN performance.  Give Microsoft 6-12 months & maybe they'll get the drivers right for their POS Win 8.1.  
    Create a restore point.
    Download & the Windows 7 (yes, seven) drivers to a folder on your Yoga.  
    Then open the following folder:
    C\Windows\System32\drivers
    Locate the file named "netr28ux.sys" and move it to a new folder you create on your desktop (for safe keeping)
    Download the Windows 7 x64 drivers for the Linksys AE6000 and the installation/setup program from the Linksys support pages here
    http://support.linksys.com/en-us/support/adapters/AE6000
    Extract those Win7 x64 files (including the netr28ux.sys file) into their own folder, then copy the extracted files to the
    C\Windows\System32\drivers  folder.
    Run the Linksys AE6000's little setup utility, insert the little nub into your USB port, complete running the setup utility, type in (or select) your network, type in your password & select your encryption type, and you should be in good shape.  
    I turn my onboard "WLAN 1" card off using the right-swipe/charms, and the Linksys shows up as "WLAN 2" with the networks it's picking up.  
    CAVEATS:  
    The Linksys AE6000 occupies one your USB ports, but the Linksys AE6000 seems to have the smallest size (barely 1" sticking out) and was rated the fastest of its size by PC Magazine.  Very good performance for .11n and .11ac environments.
    This mod may not be for everyone.  I was able to barely tolerate the Yoga's wireless limitations since purchasing in May, but the Win 8.1 rollout (along with what must be craptastic drivers) was the last straw.  The system began behavng erratically, crashing after resume, and wireless was even worse (speed degraded to 1 meg/sec or less up and download, within an hour after a reboot).  
    I have not checked the impact of this nub on battery life.  I suspect it may be a little worse than stock, but it may be a reasonable tradeoff for me to actually be able to travel more than 30 feet from my router/access point (and have YouTube stream in FHD without stutters/crashes).  
    BACKGROUND:
    After Windows 8.1 update, my Yoga 13's wireless performance went from barely adequate to useless (crashed on resume, speed degradation an hour after fresh boot, etc.).
    I'm sharing this info because I've enjoyed this machine's other assets so much.  It's too bad we can't replace the Realtek WLAN card, and obviously Lenovo though enough of our issues suffered that they chose a different card for the Yoga 2 (although the antenna design still may be partly to blame for some of those performance issues as well).   Love the keyboard, display, etc. and can put up with the fan noise (if someone has a fix for fan noise though, please post to this thread or point me to the fix).  
    Best of luck with this potential (relatively inexpensive) work-around.  It's not as ideal as switching out the internal card, but I'm pretty pleased so far.  If there are other wireless fixes, please share on this thread.  
    Thanks,
    Stanford

    Having used this thing for a couple of weeks now, I'm still amazed at how great the network performance is and how it's transformed my Yoga 13 into a near-instant device around the house (incl range that extends to the garage and perimeters of front & back yards.  And traveling is pretty phenomenal too - great speeds at the hotels we've visited (instead of having to tether my 4G phone because Lenovo's weak-sauce wireless couldn't hang onto a 1-bar connection for 3 minutes).  
    It's a small tradeoff in having a 1" by 1/8" inch "nub" stick out of a USB port, but one of the best $60 upgrades I've ever done.  Highly recommended.

  • PTR issues once the IP address range has been delegated to our name servers

    In the past, with only a DSL line, our ISP provided our forward and reverse dns entries for our zone and we never had problems with outgoing email. Recently, we've upgraded to a managed T1 line and have decided to run our own name servers on two xserves (one on the T1 subnet and one on a DSL line). Now, many email servers won't accept mail from a mail server without a matching PTR record. We've had our ISP delegate authority of our IP address range to us.
    With DNS service on, I've checked that our named.conf file refers to the db.xxx.xxx.xxx file contained in /var/named/ which contains the correct PRT entry: xxx.xxx.xxx.xxx.in-addr.arpa. IN PTR xserve.example.com.
    However, when using an external DNS server a "host name for address" search in Network Utility using the IP address, it only replies with:
    xxx.xxx.xxx.xxx.in-addr.arpa. 166154 IN CNAME 202.192/xxx.xxx.xxx.xxx.in-addr.arpa. Which refers to the IP range that our ISP has delegated to us.
    When using our xserve as the DNS server, the host name is returned correctly, though.
    Any thoughts? I've double checked with our ISP and they say they have delegated the IP address block to us.
    Xserve G5   Mac OS X (10.4.8)  
    Xserve G5   Mac OS X (10.4.8)  
    Xserve G5   Mac OS X (10.4.8)  
    Xserve G5   Mac OS X (10.4.8)  

    We had a similar problem in the past and could not explain why it was not working. The reason simply was that our carrier (the ISP owning the IP addresses) reserved the right to set PTR records only on their systems. Therefore our PTR record was simply ignored.
    So I would recommend contacting the support of your ISP/carrier, explaining your issue and let them set up the PTR record on their DNS properly.
    Edit: Sorry, noticed that it has been solved already; for any reason I saw only your first post. So ignore my reply.

  • Cisco ASA 5512x - Restrict email delivery to ip address range..

    Hi,
    I was wondering how to tighten the security of my email delivery to a range of ip addresses (I know how on my old firewall but the cisco is quite a bit different).  Right now anyone sending email to a particular ip address on my firewall can do so.  I want to restrict that to two ip address ranges it will accept deliver from.  I'm thinking I need two network objects for the two ranges then add to a network object group.  Can anyone help with configuring the ACL for delivery using that group if I'm correct about that?
    TIA
    Al

    Hi,
    I assume that you have a server or multiple servers on your network behind the ASA and want to restrict SMTP traffic to them and only allow SMTP traffic from certain address ranges?
    You might have something like this configured for the server Static NATs
    objec network SMTP-SERVER1
    host 10.10.10.10
    (dmz,outside) static x.x.x.x dns
    object network SMTP-SERVER2
    host 10.10.10.20
    (dmz,outside) static y.y.y.y dns
    If so you could simply create the following kind of configurations to restrict traffic to them
    object-group network SMTP-SERVERS
    network-object object SMTP-SERVER1
    network-object object SMTP-SERVER2
    object-group network ALLOWED-SMTP-SOURCE
    network-object
    network-object
    network-object host
    access-list OUTSIDE-IN remark Allowed SMTP connections
    access-list OUTSIDE-IN permit tcp object-group ALLOWED-SMTP-SOURCE object-group SMTP-SERVERS eq smtp
    access-group OUTSIDE-IN in interface outside
    The above configuration does the following
    Has 2 example Static NAT configurations for local DMZ servers
    Groups those 2 servers to their own object-group SMTP-SERVERS (for easier use in the ACLs)
    Creates an object-group that will contain all the public networks and host addresses that are allowed to contact your SMTP servers (for easier use in the ACLs)
    Configures an ACL that allows SMTP (TCP/25) connections from "outside" only if the source network for the connection belongs to some address range on the ALLOWED-SMTP-SOURCE object-group and when the destination is either one of your SMTP servers.
    Naturally the above object/object-group, access-list and interface names could be different and same for the actual IP addresses.
    Also, if you already have an ACL attached to your "outside" interface then naturally you use that and DONT NEED the "access-group" command above. (As its used to attach an ACL to interface which doesnt already have one attached)
    - Jouni

  • Connecting 2 WAN clouds on the same IP address range.

    Hello, I have a problem connecting my office to two third party companies.
    I have two Cisco 1700 series WAN links to my office from these companies, Both routers are fully managed by their respective companies, both use static routing, and both are using the 10.0.0.0/8 IP address range.
    The first company assigned my office the address range 10.212.1.0/24.
    The second company assigned my office the address range 10.215.1.0/24.
    My office can be set to any IP address range.
    My questions are:
    Is it possible to have a connection from my office to both networks at the same time? If so how?
    Do I require these companies to provide me with their static routing information? or can I use routing protocols?
    Do I need to perform NAT?
    Can I use a PIX 515e firewall with three interfaces?
    Sample configuration would be greatly appreciated

    It's possible to have connections to your offices at the same time with the usage of subinterfaces.The usage of static and dynamic protocols depends totally based on the size of the topology of your network.If it's a very very small network static routing will do. Performing a nat totally depends upon ypur decision whether to use a public ip or not.If required you can use a pix firewall

  • IP address range of Microsoft Location Services API

    Hi,
    I am developing a LOB windows 8.1 application. The windows 8 tablet device we are using needs to be locked down by IP address to the specific services that the application will use. I have not been able to find the IP address range for the Microsoft Location
    Sevices API uses (Windows.Devices.Geolocation namespace).
    Does someone know where on the MS website this sort of information is held as I can't seem to find this information anywhere?
    Thanks

    Probably you can find more information from here:
    https://msdn.microsoft.com/en-us/library/windows/desktop/dd464636(v=vs.85).aspx
    As I understand system have a location service and when the app calls the service, the service query the location automatically.
    If you still have questions about location service, perhaps ask at desktop forum is a better choice:
    https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=windowsgeneraldevelopmentissues
    --James
    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.
    Click
    HERE to participate the survey.

  • Site to Site VPN with Natting Internal IP address range?

    This is our actual Internal LAN address: 10.40.120.0/26 (Internal Range) and I want to translate to
    Translated address: 10.254.9.64.255.255.255.192(Internal)
    Our remote local address is: 10.254.5.64 255.255.255.192(Remote site Internal Ip add range)
    Based on above parameters I done this configuration
    access-list outside_cryptomap permit ip 10.254.9.64 255.255.255.192 10.254.5.64 255.255.255.192
    access-list policy-nat permit ip 10.40.120.0 255.255.255.192 10.254.5.64 255.255.255.192
    static (inside,outside) 10.254.9.64 access-list policy-nat
    I got all the Phase1 and Phase 2 parameters required and peer public ip add,
    I had set up vpn using ASDM before but this scenario is new for me, all I am wondering is there anything I need to configure to succesfully setup VPN

    Hi mate,
    yeah issue on far site they arent allowing access to the port we are trying to access, and they made it up and we are good to g now,
    One thing I am worried is only one IP add is able to access the resources, I mean i created an add range of 192.168.x.0/26, however only 192.168.x.3 one of our server is able to access the far site, havent got a clue
    config is as folllows:
    access-list pp-vpn extended permit ip 10.254.7.64 255.255.255.192 10.254.6.64 255.255.255.192
    access-list policy-nat---- extended permit ip 192.168.x.0 255.255.255.192 10.254.6.64 255.255.255.192
    static (inside,outside) 10.254.7.64 access-list policy-nat
    crypto ipsec transform-set esp-aes256-sha esp-md5-hmac
    crypto map outside_map 20 match address pp-vpn
    crypto map outside_map 20 set peer 172.162.1.2
    crypto map outside_map 20 set transform-set vpn1
    crypto map outside_map interface outside
    crypto isakmp identity address
    crypto isakmp policy 65 encyptio
    authentication pre-share         
    encryption des
    hash md5
    group 2
    lifetime 86400
    tunnel type ipsec-l2l
    tunnel-group 172.162.1.2 ipsec-attributes
    pre-shared-key *
    Thank you immensly for all your assitance
    ven

Maybe you are looking for