Got a linux box that has a nfs share - say its at 192.168.1.10 and the share under /etc/exports is

/some_nfs_share 192.168.1.0/24(rw,no_root_squash)

No problem right?  On another linux box within the 192 subnet, the following works quite nicely.  Assume folders exist.

mount.nfs -rw 192.168.1.10:/some_nfs_share /myfiles

No sweat, mounts right up and I get read-write so I know I did it correctly and ready for the Win2k8.  Hop over, install the unix file share stuff (NFS, SMB) and do this ...

mount -o fileaccess=777 nolock casesensitive=yes -u:root -p:* \\192.168.1.10\some_nfs_share  *

I can read files ...sort of and I can't write anything.  In the windows application logs, I get Event ID: 16397, Source: NfsClnt with this crap

The hell?  WHY are you trying to authenticate to LDAP?  I just gave you a user/pass, why would I need more than that?  Ok, FINE I bust out a local account, take that.  Nope, exactly same error.  Authen fail.  I guess I'll have to go uber-lame and go ftp.  I hate ftp.

Back in January, I was tossed into a fire regarding an environment from your absolute worst nightmare.  Yes, that bad.  It's been called a "technology showcase", "how to do everything wrong", "what happens when you have no plan" and so on -- a real top notch problem suited for those who are stupid enough given the opportunity to fix something so terrible, I didn't really know where to start. More...

I'm convinced there's a new type of phishing expedition going on in an attempt to hack search engine results.  Why?  Comments on my blog that don't add up.  For one, the magic key words the person leaves as their name.  I've dropped this as an image because I want none of those getting picked up by a search engine but its pretty clear they want an email. More...