Win2K3 Reformat, Network Shares No Longer Available

  • Thread starter Thread starter jwhardcastle
  • Start date Start date
J

jwhardcastle

I have a WinXP Pro laptop and a Win2K3 server (http, et. al.) that has
a half dozen shares I use on the laptop. I recently reformatted the
server, and now I can no longer access any shares (including ones that
are public and ones like c$ that are private) using *any* credentials.
I created my primary user account on the server just like before, and
created a few read-only accounts that work on other boxes besides my
laptop (like my *nix based DVR).

I was thinking there might be some kind of credentials that are stored
in the registry of the XP laptop that still think it's the previous
install, but I can't remember where they are.

Any thoughts? Thanks in advance.
 
jwhardcastle said:
I have a WinXP Pro laptop and a Win2K3 server (http, et. al.) that
has a half dozen shares I use on the laptop. I recently
reformatted the server, and now I can no longer access any shares
(including ones that are public and ones like c$ that are private)
using *any* credentials. I created my primary user account on the
server just like before, and created a few read-only accounts that
work on other boxes besides my laptop (like my *nix based DVR).

I was thinking there might be some kind of credentials that are
stored in the registry of the XP laptop that still think it's the
previous install, but I can't remember where they are.

Any thoughts? Thanks in advance.

Have you tried accessing the freshly installed server from a different
machine than the original Windows XP to confirm that it is a client and not
a server issue?
 
Yes, I have tried other WinXP clients, and I've tried SAMBA as well.
Everything can get through except for this one WinXP Pro laptop.

Some more background: both machines are members of the same domain, but
I'm not using domain credentials to access the shares. The server
holds no roles for the domain, and is not physically connected to the
domain (I VPN in when I need to work). I'm trying to use a local admin
account (not administrator) to authenticate. If I enter the wrong
password, it takes a while (i.e. there's an artificial delay) and then
it fails. If I enter the correct password it fails immediately saying
I do not have the correct password. Domain credentials do not work,
since I'm not connected to the domain so I can't authenticate.

When I reformatted the server, I changed the password for the account,
but not the username.

I understand that what I have here is not the best setup. I'm
temporarily 1500 miles away from my home, and will be for the next
several months. This will have to work for now.
 
jwhardcastle said:
Yes, I have tried other WinXP clients, and I've tried SAMBA as well.
Everything can get through except for this one WinXP Pro laptop.

Some more background: both machines are members of the same domain,
but I'm not using domain credentials to access the shares. The
server holds no roles for the domain, and is not physically
connected to the domain (I VPN in when I need to work). I'm trying
to use a local admin account (not administrator) to authenticate.
If I enter the wrong password, it takes a while (i.e. there's an
artificial delay) and then it fails. If I enter the correct
password it fails immediately saying I do not have the correct
password. Domain credentials do not work, since I'm not connected
to the domain so I can't authenticate.

When I reformatted the server, I changed the password for the
account, but not the username.

I understand that what I have here is not the best setup. I'm
temporarily 1500 miles away from my home, and will be for the next
several months. This will have to work for now.

You do know that you can use domain credentials UNLESS you have it blocked
in some way, right?

net use X: \\server.fqdn.or.ip\sharename /user:DOMAIN\username password
/persistent:no

Works great.
 
I've tried this in varying ways. I've tried to access it via IP, and
via FQDN. The problem with FQDN is that I have two machines that
belong to a remote domain on a different network, so I tend to stick
with IP address.

I cannot use domain credentials because there is no domain logon server
available to the host machine, so it cannot validate my credentials.
That's why I've been using local creds.

I'm nearly positive I remember something about the machine's ID being
stored somewhere, and when you reformat the ID changes. Problem is my
mind is so riddled with holes I can't even remember the proper
terminology to describe the problem. I apologize.

C:\>net use x: \\ip-address\share /USER:MACHINENAME\localaccount

System error 52 has occurred.

You were not connected because a duplicate name exists on the network.
Go to System in Control Panel to change the computer name and try
again.
 
Back
Top