Wireless Clients fail to associate with SonicPoint

November 27th, 2014 by wssra

During a troubleshooting session a few months ago, we discovered on a SonicWall NSA-250M hotfix, that after this hotfix applied, several wireless devices couldn’t associate anymore. Mainly notebooks, but smartphones and wireless HP printer could associate.

During the above mentioned troubleshooting we decided to stay with the last firmware, as the SonicWall support could not discover what was causing this problem many wireless clients couldn’t associate anymore.

Now they released SonicOS Enhanced 5.9.0.7-17o and exactly this issue is occuring. We rollback to SonicOS Enhanced 5.9.0.6-3o (or any later does the same) and the issue is gone.

Will see what SonicWall will discover when they will face loads of tickets during the next months when people with SonicPoints attached to their SonicWall environment will update to this new released firmware.

[Update]

Now when SonicOS Enhanced 5.9.1.0-220 was released we started a new firmware upgrade activity, making sure, all wireless devices have the newest wireless adapter driver installed.

When the new firmware is updating the SonicPoints, again all wireless devices can’t associate and so get no IP address. Same as on the past sessions regarding this issue.

So we rolled back to 5.9.0.6-30 again, but even after the ‘old’ firmware has also been rolled back on the AP, the clients couldn’t connect. The reason was, because the device came back with all SonicPoint configuration and profiles reset. So we had to reboot with backup settings. After this all wireless clients could connect again.

Could be, that wireless Dell clients or adapter working fine with the new firmware, but we will not support such politics.

If you don’t want to run into such a situation to be forced to replace a large number of wireless devices because of future firmware updates, you better look for more serious and reliable solution vendors.

Remote Desktop Services – Upgrade and Migration Guidelines for Windows Server 2012 R2

January 31st, 2014 by wssra

Microsoft Remote Desktop Virtualisation Team has published a detailed guideline and walkthrough to migrate Remote Desktop Services from Windows Server 2008 R2 to Winows Server 2012 R2 and hints how to migrate or update Remote Desktop Session and Virtualization Hosts as well Remote Desktop Web Access and Connection Broker roles.

You find details here .

 

Problem with new iTunes 11.4.1 on Windows 7 64-bit Clients

January 28th, 2014 by wssra

It seems to be a known issue for the last update for iTunes. Your update will fail and iTunes may not work properly after this.

So better wait for an update from Apple which may solve this.

One option may be a removal of this component as described in the following article

http://support.apple.com/kb/HT1923

 

Skype blocks your network adapter [Update]

April 27th, 2013 by wssra

Since Skype versions 6.1x and especially 6.2x and now 6.3x many people facing problems with network connections after starting Skype. Even not be able anymore to logon to Skype, because the network connection is blocked.

When you open the status for your network adapter, you can see that there are not any byte received and send anymore. And after a few seconds you get notice that there is no internet connection anymore.

Not enough, you recognize starting IE or Explorer takes time, if you are anyways be able to open them.

Once you terminate Skype everything returns.

It doesn’t matter if you disable UPnP in Skype or you disable using alternative port 80 or 443 to receive incoming calls.

Sometimes it helps for a while if you let the network wizard resolve problems with the network connection. But be aware that the issue returns when you start Skype next time.

If you find event ID 11609 in your event log referencing to your Skype installation, this is related to what I described.

Here are some links if you like to read more about…

https://jira.skype.com/browse/SCW-4113

http://community.skype.com/t5/Windows-desktop-client/Skype-6-3-won-t-run-past-login/td-p/1472382

[Update]

After applying KB2444677 Hotfix, Problem was solved. So it seems it is related with special handle execution on Explorer internals.

[Next Update]

Problem turns back until it was solved for a while. Now thinking about finish with Skype, as this seems ongoing issue when reading community forums.

[Additional Update]

Seems now been fixed with Skype version 6.3.0.107 hopefully

 

 

WLAN–LAN switch not supported under Windows 8

April 27th, 2013 by wssra

Maybe you remember setting the WLAN / LAN switch on your notebook BIOS, disables your WLAN adapter when you plug in an Ethernet cable to your NIC and enables the WLAN when it is unplugged.

This feature, even if it is correctly configured in the BIOS of your notebook, it will not work on Windows 8.

Sadly you have to manually switch adapters on or off under Windows 8

 

Internet Explorer crashes and hangs

April 1st, 2013 by wssra

Starting with IE10 installed, I faced lots of crashes and hangs.

Searching for some troubleshooters I found this helpful

http://blogs.technet.com/b/yongrhee/archive/2013/03/31/internet-explorer-crashes-or-hangs.aspx

 

Hyper-V Virtual Machines SID permission issue

February 14th, 2013 by wssra

If you want to move VHD files you have to take care on certain permissions on configuration files and directory rights. Otherwise you will not be able to start your VM.

For more details and how to solve this read this articles.

http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/storage-management/hyper-v-file-storage-permissions.html

http://architectevangelist.wordpress.com/2011/02/20/hyper-v-virtual-machines-security-group-issue/

 

Recover Exchange Mailbox Database with SCDPM

February 14th, 2013 by wssra

Recently we had to recover Exchange databases and it works like charm and described here.

Before starting process you have to enable to overwrite database in EMC on the database properties.

 

Exchange Server 2010 Service Pack 3 released

February 13th, 2013 by wssra

This is a mandatory service pack to run Exchange 2013 in the same organization. And mandatory to run Exchange 2010 on Windows Server 2012.

Several other enhancements have been implemented now. So also Internet Explorer 10 is supported to use for Exchange mailbox access.

More details here.

Windows Server Failover Cluster 2012 in Depth

July 24th, 2012 by wssra

Find here all sessions from Tech-Ed which covers all details about Windows Server Failover Cluster 2012. Every session takes about one hour. But it is worth taking time watching all of the sessions.