Posts Tagged “microsoft”

After upgrading a Windows Server 2003 clustered file server to Windows Server 2008, Mac OS X 10.5 clients would no longer connect to the file server.  After much searching, I found that Microsoft changed something about share name scoping on clustered resources causing non-Microsoft clients to fail.  Of course, Microsoft blames Apple and Apple blames Microsoft for incompatibility issues which really doesn’t help anyone.

I found one work-around to the problem for Mac OS X clients – In Mac OS X finder, use Cmd-K to bring up the Connect to Server dialog.  For the server address, use either:

smb://fileserver:139/sharename
or
cifs://fileserver:139/sharename

Share browsing of the server doesn’t seem to work so you need to specify the share which you want to connect to and specifying port 139 seems to fix the problem.

Weird stuff.  Not sure who to blame on this one really but I expect a little better compatibility on these “enterprise” class products.  As a side-note, these changes to clustered file sharing even causes issues with Exchange 2007 running on a Windows Server 2008 cluster.  When Microsoft can’t even get their own software to work correctly, I think it’s easier to know who to blame.

Comments 15 Comments »

A couple people at work pointed out that support.microsoft.com would not load when browsed through the squid proxy cache.  However, it would work if you could browse directly to the site with no proxy between.  Some web searching turning up the following information that support.microsoft.com somehow managed to break itself when browsing through squid.  To correct the issue, add the following lines to your squid.conf:

# Fix broken sites by removing Accept-Encoding header
acl broken dstdomain support.microsoft.com
header_access Accept-Encoding deny broken

Restart squid with squid-k reconfigure and support.microsoft.com should be working again.

On a somewhat related note, Windows XP service pack 3 was loooong overdue.  I found a Microsoft hotfix today for Windows XP going back to 2006 that fixes kernel problems when over 1Gb of RAM is installed.  Unfortunately this fix never made it in to the automatic update channel but it has been included in SP3 – which was only release 3 weeks ago.  I guess when XP came out in 2001, not a lot of Microsoft engineers thought it would still be used quite heavily 7 years later.  Vista?  Pth…try again, Microsoft.  Mac OS X 10.5 seems to be the most modern operating system right now.  It may not be perfect (is anything truly perfect though?) but it’s still much better than Vista.

Comments Comments Off

After upgrading to Vista SP1, I ran in to some problems between my computer and my Fedora Core 6 Samba 3.0.24 server.  I have my Wordpress software directory mounted from the Linux server to my Vista SP1 computer to make adding plug-ins easy.  All I do is copy the new plug-in from my computer to the Wordpress share and it is added.  This worked fine until a few days ago when I suddenly started to get “access denied” when copying the files.  I concluded the problem was the fault of Vista SP1 after the following troubleshooting:

  • No changes had been made to the Samba configuration for quite some time.
  • All file permissions on the Samba server were correct.
  • Mac OS X Leopard was functioning correctly with no changes required.
  • Windows XP SP2 was functioning correctly with no changes required.

After checking the latest version of Samba (3.0.28a at this time), it mentioned that it corrects “interoperability issues” with Vista SP1.  To correct these issues, follow these steps:

Download the Samba 3.0.28a source RPM for Fedora Core 8
Install it: rpm -ivh samba-3.0.28a-0.fc8.src.rpm
Build it: rpmbuild -bb /usr/src/redhat/SPECS/samba.spec
If you get warnings about dependencies, either download the dependent packages through yum (yum install …) or use the –nodeps option with rpmbuild.
Watch some Battlestar Galatica while the package builds…
Install it: rpm -Fvh /usr/src/redhat/RPMS/i386/samba*
This will update only the RPMs that are already installed.

Test the new installation and your Vista SP1 problems should disappear!

Comments 3 Comments »