Enabling WPS on a Billion BiPAC 8900AX

Posted on by treaclepumpkin

By default WPS is disabled on the 8900AX, so if you need to connect a device, TV, printer etc, using WPS then you will have to go into the Configuration menu and enable it.

  • This can be found under the Configuration->Wireless 2.4G->Security menu.
  • Select the “Enable” value for the “WPS” combo, under “WPS Setup”.
  • Ensure that the “Add Client” option is set to “Use STA PIN”.
  • Make sure that the “PIN” value is blank.
  • Leave all other options at their default settings.

Once this is done all you need to do, to connect the device using WPS, is to press the WPS button on the router, for around a second, and then perform the equivalent activity on the device you want connected.

The current identity (IIS APPPOOl\xxxxxxx) does not have write access to…

Posted on by treaclepumpkin

If you encounter the following error then this may be the fix you’re looking for.

Server Error in ‘/’ Application.

The current identity (IIS APPPOOL\xxxxx) does not have write access to ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files’.


Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The current identity (IIS APPPOOL\xxxxx) does not have write access to ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files’.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): The current identity (IIS APPPOOL\xxxxx) does not have write access to ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files’.]
System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +10003412
System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException) +204

[HttpException (0x80004005): The current identity (IIS APPPOOL\xxxxx) does not have write access to ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files’.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +9947380
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +101
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +456

 

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1055.0

Simply run this code, from the Developer Command prompt: aspnet_regiis -i

Update 3-Jul-17:
On Windows Server 2012 you may need to run this command:

dism /online /enable-feature /featurename:IIS-ASPNET45 /all

 

How to stop Google using your SSID for location services

Posted on by treaclepumpkin

Just found out that you can stop this.

By default, Google, and possibly others, use your SSID to help improve their location services. You can opt out by changing your SSID, shouldn’t it be if you want to opt in? Anyway if you add “_nomap” then they won’t record your data, alternatively maybe hiding the SSID does the same?
More details here: https://support.google.com/nexus/answer/1725632?hl=en&rd=1

Debugging multiple websites from one solution? Breakpoints not being hit?

Posted on by treaclepumpkin

If you see this tooltip when examining your break points “The break point will not currently be hit. No symbols have been loaded for this document” then you’ve found the same issue that has been driving me mad for a few hours, it must mean you’re new to debugging web sites as well!

Simple solution (sic) is to right-click on your solution file and select “Properties” and then under Common Properties->Startup Project select the “Multiple startup projects” and set whatever action you require against the project(s) you want to debug.

Simples! Applies to Visual Studio 2010 onwards, and not just VS2013 as I at first thought.

Cross Origin Resource Sharing or using ajax sensibly

Posted on by treaclepumpkin

By default ajax requests that go across domains are blocked by most modern browsers, read Chrome, Firefox and Internet Explorer 8+.

To enable this functionality you need to add new headers to your sever specify the domains that can access your data or just let anyone in.

Full details can be found here: http://enable-cors.org/index.html

If you cannot be bothered to read the article then you just need to add the following headers.

  1. Access-Control-Allow-Headers – Try X-Requested-With, Content-Type, Accept
  2. Access-Control-Allow-Methods – GET, POST, PUT, DELETE, OPTIONS
  3. Access-Control-Allow-Origin – *
  4. Allow – GET, POST, PUT, HEAD, DELETE, TRACE, COPY, LOCK, MKCOL, MOVE, PROPFIND, PROPPATCH, UNLOCK, REPORT, MKACTIVITY, CHECKOUT, MERGE, M-SEARCH, NOTIFY, SUBSCRIBE, UNSUBSCRIBE, PATCH, SEARCH

Obviously the above is over kill and can be cut down to meet your specific requirements.
For example (2) could be reduced but you may find you have to keep the OPTIONS value in as this can be issued by the browser before a GET or POST to determine what the server supports (a preflight request).
The value of “*” for (3) allows any site to access your data using XmlHttpRequest, this could be reduced to a list of space separated domains if required.
The final list (4) is again over the top and could be reduced significantly.

If you happen to be using OAuth 2.0 then and sending the access_token via the header, rather than the querystring, then you need to add Authorize to the Access-Control-Allow-Headers, as the token should be sent using the Bearer field.
In fact if you use any custom headers then you’ll need to add them all as CORS strips them all out.