Some things I agree with
(or not as the case may be)
Friday, April 11 Windows error codes, know thy master
Those fscking Windows error codes really annoy me sometimes - how am I supposed to remember what 0x00002740 stands for? (It's "Only one usage of each socket address (protocol/network address/port) is normally permitted. WSAEADDRINUSE" aka errorcode 10048, incidentally).
If, like me, you don't have a photographic memory (or months to memorise what each code stands for), there's a couple of useful links you should have bookmarked:
All the pirates proper are wondering what all the fuss is about - piracy of Vista has continued unabated since its launch, with patches and workarounds galore for the WGA checks and suchlike, so why is Microsoft even bothering to do this now? They've utterly failed with Vista, they should just drop it and revert to a previous point revision in the SVN where, at the very least, the Start Menu worked - and then build AROUND those smaller features, instead of making section developers have to recode their own sections due to the whims of the core dev team. And to think I thought XP was a mess until I used Vista...
Christmas is nearly upon us, so look forward to seeing me looking grumpy in a santa hat again. December just wouldn't be the same without it.
Dragged out of Christopher's memory and pasted
into his blog at
12/04/2007 04:35:00 PM. Roughly. Blog ID: 2060156806331041534·
Sunday, September 30 Having problems with your Windows shares? This might help
This might be the magic command which fixes them...
I've been having a problem with getting a laptop running XP Pro to see (and be granted read/write access to) shares on a Windows Server 2003 box. In a nutshell, I'd fire up a share via Run (
) and it might once ask me for a username and password, which I'd type in, and then I'd be granted access, but after that I'd just be kicked back to the logon dialog again. The WS2003 machine was showing ANONYMOUS LOGON attempts - apparently null sessions that Windows uses to authenticate the user - which were succeeding, but the username I was supplying wasn't being authenticated for some reason. This laptop is the only device I've used or set up which has had this problem, and it's been driving me nuts.
I hate Windows filesharing almost as much as I hate using Macs. ;)
Anyway, I eventually gave up trying to fix it on my own, and decided to give Google a shake and see if any answers fell out of its pockets. Lo and behold, similar problems were being discussed on places like Experts Exchange, and I clicked through to one of them. ("Error: \\pc name is not accessible. You might not have permission to use this network resource...Access is denied." When trying to access a share.")
Some way down the page, a guy called dvt_localboy wrote,
What is happening there is that your XP Home machine is trying to connect to the XP Pro machine with 2 different sets of credentials. I suspect that you've enabled the quick logon option, which caches network drive info aswell.
Try net use * /d to disconnect all network connections on the XP Home machine, even connecting via IPC$ uses a specific set of credentials, which could conflict with any other type of connection that you may be trying to connect with later.
Filled with anticipation, I fired up a DOS box on the laptop (using VNC, that was the most annoying thing - I could VNC to the laptop fine! haha) and typed in
net use * /d
. I then immediately fired up a share, this time the hidden root share
, typed in a username and password which had admin rights on the server.... And bingo! It worked!
So, if you're having odd, unpredictable bouts of inaccessible network shares, that command might just do the trick. I'll stick it in my brain for next time, that's for certain.