Mr Andersson

Archive for the ‘troubleshooting’ Category

Enable-PSRemoting is broken in PowerShell?

with 2 comments

Yesterday I installed the RTM bits of WinRM 2.0 on a Windows Server 2003 machine and it were really no issues at all getting it working.

Today I tried to do the same thing but on a Windows 2008 Server (R1) that is not joined to any domain, and it fail on step 1 of the configuration.
In both cases I started out downloading the patch. Then I run “Enable-PSRemoting” in an elevated PowerShell prompt, which succeeded on the Windows 2003 Server but not on the Windows 2008 Server.
The error I got was “Access denied”.
I thought I followed the troubleshooting guide for WinRM, but apparently there is slight difference of two different ways I found on how you set this up. You can either run “Enable-PSRemoting” or you can run “winrm qc”. If I run the quick config tool using the “winrm” command everything works out just fine, but if I use “Enable-PSRemoting” I get “Access denied”.
The most mysterious part of this is that “Enable-PSRemoting” WORKED on Windows Server 2003, but not on Windows Server 2008. Strange!
If you have any clues about this, please leave me a comment!
Advertisements

Written by anderssonjohan

November 18, 2009 at 07:57

Posted in scripting, troubleshooting

Tagged with ,

Note to self: If you get error code 12250 from ISA server 2006…

leave a comment »

“Error Code: 403 Forbidden. ISA Server is configured to block HTTP requests that require authentication. (12250)”

Everything works from and to the protected networks but traffic from the external network is blocked with the error response above.
Solution: Stop using the darn “Publish web site” wizard and copy already existing stuff 🙂
-or- make sure that the “Allow client authentication over HTTP” check box is checked.
Found at the HTTP Listener properties – Authentication tab, click Advanced.

Written by anderssonjohan

November 17, 2009 at 07:30

Posted in troubleshooting

Tagged with ,

How I succeeded to configure Pidgin to work with our Office Communications Server

with 7 comments

Since it was a real hassle to figure out these settings I decided to note them here for future references. Since I didn’t find this variant of the Pidgin+SIPE+LCS configuration anywhere else, it may be useful for others too.

While talking to others using Pidgin + LCS I noticed the configuration may differ depending on your setup, i.e. internal only or external LCS / SIP server.
At work we use an internal only LCS server which is only listening on its default TCP port (5060).
Below you can see that I need to enter domain + username in the auth* fields. I know others that don’t use these fields in their setup, but they do have an externally accessible (over TLS/SSL, port 443) LCS / SIP server.
So be prepared, your result may vary :).

  1. Download Pidgin (v2.5.5 in my case)
  2. Download SIPE (v1.3.3, libsipe.dll, precompiled dist for Windows)
  3. Put libsipe.dll in the plugins directory of Pidgin
  4. Go to Accounts -> Manage Accounts
  5. Choose Add..
  6. Enter the following settings.

    Tab: Basic
    Protocol = Microsoft LCS/OCS
    Username = <your SIP address in Active Directory is your primary e-mail address>
    Password = <your Active Directory password>

    Tab: Advanced
    Use Proxy = Checked
    Proxy Server = <the FQDN of your LCS server, i.e. mylcs.corp.local>
    Use non-standard port = Checked
    Port = 5060
    Connection Type = TCP
    Auth User = <your Active Directory username>
    Auth Domain = <your Active Directory domain name in dotted form, i.e. corp.local>

  7. Click Save and you should see your LCS contacts appearing in the Buddy List of Pidgin

All Done!

Written by anderssonjohan

March 16, 2009 at 11:02