On pfsense, make sure to update your UDP multiple state timer. It’s in System->Advanced->Firewall & NAT

By default it is set to 15 seconds, and phones refresh their WiFi Calling tunnels at 60 seconds on iOS, and 60+15 random seconds on Android. You should set it to at least 90 seconds to prevent tunnels from being closed prematurely. I recommend setting it to 900 seconds (15 minutes).

You’ll know you need this if you miss incoming calls, or they randomly go to voicemail, and if you have delays in incoming text messages. You’ll also see sessions with low state timers in Diagnostics: pfTop (filter for “udp port 4500” to see all active WiFi Calling sessions bidirectionally)

In this case, he was using a pfsense firewall, but it’s the same problem. On the Barracuda firewalls, creating a firewall rule with UDP timeouts increased on UDP port 4500 will resolve it.

speedtest-cli

You should get a response that looks like this..

Hope this helps.

Username: cusadmin
Password: highspeed

Recently though it seems like some of the newer modems like the wireless gateway TC8305C use the following combination.

Username: admin
Password: password

For all the folks out there still running Windows XP, you will be in for a surprise when you go to upgrade Quickbooks. Starting with Quickbooks 2015, you can not install it on Windows XP. I haven’t tried all the possible workarounds yet, but the installer will check to see if you are running Windows XP and will prevent you from continuing. You can also see the list of requirements for Quickbooks 2015 here.

If I discover a workaround, I will post it. However, I highly recommend that you upgrade to Windows 7 or later. It’s way past time for you to upgrade.

Cannot start Microsoft Outlook. Cannot open the Outlook window. Invalid XML, the view cannot be loaded.

Starting Outlook in safe mode didn’t work either. Fortunately the fix is really easy.

If you are on Windows 7 simply type the following command in the search or run box.

Outlook.exe /ResetNavPane

Bingo. You will be up and running again!

Thanks to itswapshop.com for the tip.

The problem is when the Update Now button is clicked, you get a notice saying you’re up to date! Restarting the program will bring the error message back again.

I haven’t found a good solution for this problem yet, any ideas?

I’ll update this post if I find something.

Fortunately there is a fairly easy workaround for this issue. Yup, you guessed it. Powershell!! This article gives step by step instructions on how to add a domain to your office 365 account via powershell. Here are the concise steps if you are already used to using Office 365 & Powershell.

1. Connect to your Office 365 account using the command “connect-msolservice”. (without quotation marks)
2. Use the “New-MsolDomain” cmdlet to add your domain. Just like this “New-MsolDomain -name example.technology”
   

Bingo! It works.

I was even able to verify the domain

The problem is I’m now stuck on Step 2. Which is the step where you need to “Setup Office 365 and keep your website where it’s hosted today”. It gives an error message that “Sorry, we couldn’t save that. Please try again.”

Grrr.. So I’m still stuck. If anyone has any tips, feel free to comment. Otherwise I’ll update this post once I figure out to continue.

Update 3/3/2014: I’ve discovered that at this point it is not possible to use a generic top level domain with Office 365 Small Business and Office 365 Small Business Premium. I upgraded my account to Office 365 Mid Sized Business, and I was able to add, verify, & activate the domain name following the steps above. So in short, if you want to use a new cool domain name, make sure you are using Office 365 Mid Sized Business plan or any of the Enterprise plans.

[note]”Error 0x2077 Illegal modify operation. Some aspect of the modification is not permitted.”[/note]

I was a bit stumped until I read a few of the comments on that article. If you are experiencing this error, check out these tips by Brandon in the comments. Worked perfectly after I followed these steps. Thank you, kind sir.

• Insure that you are connecting to your DC by using LDAPS (SSL, port 636)
• When performing the rename operation using LDP.exe, insure that you are changing the distinguishedName to an object that doesn’t exist. In my case, I received this error when I forgot to include the computer’s name in the DN (meaning, I only had OU=x,DC=y,DC=z instead of CN=Server,OU=x,DC=y,DC=z)
• If using powershell and you receive this error: use LDP.exe and insure you are using LDAPS and a DN that doesnt exist

At this point it appears the fix is to install this hotfix available from Microsoft.  Update: Hotfix has been pulled for some reason.

Update: Microsoft has published a Technet article detailing this problem with some resolutions.

Update: Microsoft has now published an Outlook 2013 Update to fix this.