经验内容仅供参考，如果您需解决具体问题(尤其法律、医学等领域)，建议您详细咨询相关领域专业人士。
请扫描分享到朋友圈你的位置： >
> Win8.1连接wifi受限怎么办 Win8.1无线网受限的解决办法
经常有一些Win8.1笔记本用户会遇到连接wifi受限的情况，导致电脑无法正常上网。以下小编为大家汇总整理了几种常见的Win8.1无线网受限的解决办法，目前已经有诸多网友通过此方法解决了问题，希望对遇到类似电脑问题的朋友会有所帮助。
Win8.1连接wifi受限怎么办 Win8.1无线网受限的解决办法
导致Win8.1连接wifi受限主要有几种情况，比如无线网络设置不当、驱动版本过低、Wifi网络本身有问题等。下面我们分别来看看，大家可以根据以下情况一一排查下。
一、首先确保Wifi无线网络可用
有时候，由于Wifi无线网络本身故障，即便可以连接，但无法上网。对于这种情况也可能会出现Win8.1连接wifi受限无法联网。如果大家Win8.1电脑无法连接Wifi无线网络，可以试试使用智能手机/平板/笔记本设备连接试试，看看是否可以上网，如果连接同样是受限，那说明是无线网络本身问题，与Win8.1系统无关。如果其他无线设备可以正常连接Wifi，说明是Win8.1电脑问题，那么继续往下看。
二、检查无线网络是否勾选“为此网络启用联邦信息处理标准”
1、打开Win8.1桌面最左下角的Windows图标上右键，然后选择打开“网络连接”，如下图所示：
2、打开网络连接后，然后在无线网络名称中，点击右键，然后点击“状态”，如下图所示：
3、进入无线网络状态设置后，再依次点击“无线网络属性”，打开无线网络属性后，切换到顶部的“安全选项”，接下来再点击底部的“高级设置”，如下示意图所示：
4、最后在高级设置中，勾选上“为此网络启用联邦信息处理标准”，完成后，一路点击底部的确定保存即可，如下图所示：
Win8.1系统默认并没有勾选上“为此网络启用联邦信息处理标准”此项，部分Win8.1连接wifi受限用户通过勾选上此项设置，成功解决Wifi无线受限或者网络不稳定的情况。
三、更新网卡驱动 如果以上两种方法仍旧没有解决问题，那么建议大家更新一下无线网卡驱动，更新网卡驱动并不难，大家可以借助鲁大师、驱动精灵等软件，一键检测更新网卡驱动。 对于更新网卡驱动不太熟悉的朋友，请
三、更新网卡驱动
如果以上两种方法仍旧没有解决问题，那么建议大家更新一下无线网卡驱动，更新网卡驱动并不难，大家可以借助鲁大师、驱动精灵等软件，一键检测更新网卡驱动。
四、试试断网急救箱
如果通过以上三种均无法解决Win8.1连接wifi受限怎么办？对于这种情况，笔者建议大家使用360安全卫士的断网急救箱，一键修复上网试试。使用方法如下。
1、打开360安全卫士（适合此前电脑中已经安装了该软件，此前没安装的用户，可以用U盘其其他电脑下载拷贝一个到自己电脑安装即可），进入主界面后，点击右侧“功能大全”后面的“更多”，如下图所示：
2、进入功能大全后，就可以找到“断网急救箱”工具了，点击打开即可，如下图所示：
3、最后断网急救箱会自动检测电脑网络环境问题，如果有问题，我们按照提示点击修复即可，如下图所示：
通过这种方法也可以解决很多Win8.1连接wifi受限电脑问题，大家可以试试。
通常来说，如果Win8.1用户遇到连接Wifi受限，采用以上四种方法一一排除，都可以解决问题，遇到类似问题的朋友，快去试试吧。
与本文相关的文章新买了个wp8系统的手机，电脑还是猫不是带有无线网卡的，怎么连wifi_百度知道
新买了个wp8系统的手机，电脑还是猫不是带有无线网卡的，怎么连wifi
买限路由器或随身wifi类产品手机连接wifi网
其他类似问题
按默认排序
其他2条回答
= =连接都没WIFI买带WIFI路由器吧
买个无线路由器啊
无线网卡的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁Windows Phone 8.1 会自动接入可信赖的 Wi-Fi
觉得在咖啡店里要「翻越」重重网页才能用上 Wi-Fi 实在太过麻烦？最新的
应该能帮你省下不少功夫。它内建的 Wi-Fi Sense 功能会自动接入那些可信赖的免费无线网络，而且你还可以用它将路由器密码安全地分享给 Facebook、 及 Skype 联系人。感觉上是个颇为实用的功能，但能否成为卖点就要看支持的 Wi-Fi 服务范围有多广了。
引用来源：
消灭零回复，从我做起。免费共享wifi密码？总担心会不会同时传些个人隐私给NSA miui曾经有这么一个功能 结果被群起攻之 不得已只能取消这个功能···· 和邻居互加Facebook的重要性 老婆拿着老公的wp8.1去闺蜜家自动连上wifi也就能说通了Background file transfers for Windows Phone 8
Background file transfers for Windows Phone 8
Applies to: Windows Phone 8 and Windows Phone Silverlight 8.1 | Windows Phone OS 7.1
With Windows Phone OS 7.1, applications are able to queue up one or more file uploads or downloads over HTTP that will be executed in the background, even when the application is no longer running in the foreground.
The APIs used for initiating file transfers should be used to query the status existing transfers and provide progress indicators for the end user. For a step-by-step walkthrough of creating an application that uses background file transfers, see .
This topic contains the following sections.
The background transfer service APIs can be found in the
namespace. The primary programming elements you will use are the
classes. The BackgroundTransferRequest object represents a single transfer request including the target and destination file paths, the transfer method, and the current status of a transfer.
The BackgroundTransferService object is used to initiate new transfers and to query for or remove existing file transfers.The Background Transfer Service only supports transfers using HTTP and HTTPS. FTP is unsupported. You can upload and download files in the background with the BackgroundTransferService. The GET HTTP method is supported for downloading files, and the POST method is supported for downloading or uploading files. Set the method for a transfer by using the
property of the BackgroundTransferRequest object.All background transfers require a local file path. Downloads require a destination path that specifies the location at which the downloaded file will be saved. Uploads require a source path that specifies the location from which the file will be uploaded. All local paths for background transfers must be within the isolated storage for your application within a root directory named “/shared/transfers”. This directory is created by the operating system upon application installation, but if your application deletes or renames this directory, you must re-create it before initiating any file transfers. You can create any additional directory structure you choose underneath the root “/shared/transfers” directory, and you can copy or move files after the transfer is complete to ensure that the background transfer service does not modify the files, but attempting to initiate a transfer using a path outside of the “/shared/transfers” directory will throw an exception. The
property of the BackgroundTransferRequest object is used to set the HTTP headers for a transfer request. The following headers are reserved for use by the system and cannot be used by calling applications. Adding one of the following headers to the Headers collection will cause a NotSupportedException to be thrown when the
method is used to queue the transfer request:If-Modified-SinceIf-None-MatchIf-RangeRangeUnless-Modified-SinceBackground transfers initiated with the Background Transfer APIs will typically begin as soon as the requirements set by the
property as well as system requirements related to battery power and available connections are met. However, because multiple applications may have background transfers queued up, there may be an additional delay before transfers begin while previously added transfers complete.Windows Phone 8 introduces the Data Sense feature which allows users to request that apps limit data transfers as they approach the limit for their data plan. If the user has turned on the feature, background transfers may be paused depending on the values of following members of the . – If this value is true, background transfers will proceed regardless of whether the app is currently running in the foreground. – If this value is true, background transfers will proceed only if the app is currently running in the foreground. – If this value is true, background transfers will be paused regardless of whether the app is currently running in the foreground.For more information on the Data Sense feature and how your app can use it to adjust data usage, see .Important Note:In addition to the requirements for general applications, there are additional certification requirements for applications that use background file transfers that must be met for an application to be listed in Store. You should consider these requirements as you design and implement your application. For more information, see .The operating system enforces a number of restrictions on background transfers related to file size, connection speeds, and device resources. This section lists the policies for background transfers for Windows Phone. Note that the Windows Phone Emulator simulates a device that is connected to Wi-Fi and external power. To verify that an application works under other conditions, you should test on a physical device.Maximum upload file sizeOver cellular connection - 5 MBOver Wi-Fi connection with battery power - 20 MBOver Wi-Fi connection with external power - 100 MBMaximum download size over cellular connection20 MB – If a file exceeds this limit, the
property for the transfer is automatically changed to , which has the effect of requiring Wi-Fi for the transfer.Maximum download size over Wi-Fi without external power100 MB – For files larger than 100 MB, you must set the
property of the transfer to
or the transfer will fail. If you do not know the size of a transfer and it is possible that it could exceed this limit, you should set the value to None, meaning that the transfer will only proceed when the phone is connected to external power and has a Wi-Fi connection.Maximum outstanding requests in the queue per application (this includes active and pending requests).25 – Transfers are not removed from the queue automatically when they complete. Applications should use
to remove completed transfers from the queue to keep the slots free for new transfers.Maximum concurrent transfers across all applications on the device2Maximum queued transfers across all applications on the device500Maximum number of HTTP headers per request15Maximum size of HTTP headers16 KB eachThe background transfer service will transfer on the following data networks while the app is in the foreground. Transfers will not proceed on these networks while the app is not in the foreground. This limitation is shared by the
object, so in this respect performing your own transfer does provide any advantages over using background transfers.2G, EDGE, Standard GPRSOn networks that are 3G and higher, background transfers will proceed regardless of whether the app is running in the foreground, assuming all other conditions are met.The content-length header is required on the server side for files greater than 5 MB. Servers should always return the content-length in responses. Failing to do so can result in severely degraded transfer performance.Range headers are required on the server side for files greater than 5 MB. Servers should always support range request headers. Failing to do so can result in severely degraded transfer performance.If the network connection of the device drops below the following rates, the transfer will be paused and retried. These limits, expressed in kilobits per second (Kbps), are low and will not typically be hit.Network mediumMinimum data rate3G50 KbpsWi-Fi/USB100 Kbps
Was this page helpful?
Your feedback about this content is important.Let us know what you think.
Additional feedback?
1500 characters remaining
Thank you!
We appreciate your feedback.
Related developer sites
Other Windows sites
Tool and product downloads
Design template downloads
Essentials
Hello from Seattle.