Hello Siminlal & mabe2010:
For Siminlal, I've tried to invoke/activate NTLMv2 on the Server & have re-booted it several times, but w/o any luck. It seems to accept the Service, but I've not found anyway to specifically "start" v2 despite changes to the Policy Editor. I found a "vague" (really do mean vague !) description of a solution off of MSTech Site w/change to the Registry that I tried but thus far am still having same problems.
Mabe2010, thanks for the tip, I think that I've tried that as well, but will give it a go. All of my efforts to "map" a drive have thus far met with FAILURE. In my instance I can see the Domain on the Network - "xyz" Server but cannot access any of the files. I've tried direct login, mapping to the C$ and also in my case since the drive is split to the Data$ "defined" sub-directory w/o success. I've also attempted to login as both Administrator (Domain) w/Admin password and as a newly created Credential - e.g. Dave (Admin equivalent) w/new password with no success. What is "bizzare" to me is the format that is returned - i.e. - Win7 (computer name)\Administrator or Dave or XXX regardless of what is submitted. To compound this issue, neither Vista (Home Premium) and/or XP et al (in various incantations from SP1-3 & MCE) have had any problems. The only other non-mentioned item is that my Win7 (as is my Vista) is x64 bit, though as noted it has not been a problem with Vista.
For all, I've posted similar ? at the Microsoft site on the Tech side and have only gotten back the response that Home Premium can't join a Domain - duh! To me and maybe others, this does seem to be a "failure" for the NEW OS! I love the looks, I like the quicker access, I've heard of problems with various drivers (but have not yet experienced those) but I've got to have my DATA! My server is my life blood because it keeps on "ticking"!!! I can't even recall the number of times XP/MCE/Vista has "crapped" out on my local machine(s), but that Server (Win2K) has saved my "bacon" - What a disappointment if its no longer useable!
Dave
PS - Forgot to mention that I even changed from "Workgroup" to the Local "name" defined by the Server w/o any change or improvement. After looking at everything for a while, I thought maybe that might be causing it a problem in recognizing an accessible computer (foreign vs native) member of the "group". Still no help. My only other thought might be to try a VNC access but that's pretty far out there.
Dave