Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.
Can't connect (MAP) to a share on XP from Windows 8.1
I get an invalid password error message when I try to make a network connection to a share on a Windows XP machine from a Windows 8.1 machine. I know that this has worked before as recently as a month ago. I have a Windows NT shell script that I have used for doing backups from PC to PC that I have used for years. I wrote it myself when I used to do that kind of thing on a regular basis. And I know that I have used it successfully between these 2 machines within the last month. I haven't been doing much network stuff for years that I used to do on a regular basis when I was working as a programmer that knew enough about Windows networking to be better than just dangerous.
Please see attached screen shot. It shows the domain that I am being authenticated by as HP003. That is the machine that I am logged on to right now. I haven't joined that machine to a domain just because I don't want to for now. So when I logon to that machine it is always with a local UID and PW. And it always works including when that machine times out and I have to press ctl-alt-del to get back in. I thought I remembered that is the credentials that I use to map a drive letter on HP003 to a share on IBM003. But for some reason now it won't work. What the hell am I doing wrong?
Thank you for any help you can provide me.
Please see attached screen shot. It shows the domain that I am being authenticated by as HP003. That is the machine that I am logged on to right now. I haven't joined that machine to a domain just because I don't want to for now. So when I logon to that machine it is always with a local UID and PW. And it always works including when that machine times out and I have to press ctl-alt-del to get back in. I thought I remembered that is the credentials that I use to map a drive letter on HP003 to a share on IBM003. But for some reason now it won't work. What the hell am I doing wrong?
Thank you for any help you can provide me.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I have a network of mostly XP machines. Every now and then, they don't want to talk to each other. The only thing that seems to fix it is to go to the 'other' machine and connect from it.
Dave,
That is interesting and possibly useful to know. But for what I am trying to do I need the drive letter mapping to be on HP003 because that is where my Windows NT shell script compresses the directories I am backing up by having the output of the WinZip compression process be on the drive letter mapped to the share on the IBM003 machine. I haven't even considered having the WinZip compression process run on IBM003 from a drive letter mapped back to HP003. I'll have to take a look at the possibility of doing that tomorrow.
Thank you.
That is interesting and possibly useful to know. But for what I am trying to do I need the drive letter mapping to be on HP003 because that is where my Windows NT shell script compresses the directories I am backing up by having the output of the WinZip compression process be on the drive letter mapped to the share on the IBM003 machine. I haven't even considered having the WinZip compression process run on IBM003 from a drive letter mapped back to HP003. I'll have to take a look at the possibility of doing that tomorrow.
Thank you.
I wouldn't assume anything at this point. It has seemed to me that XP networking doesn't always work quite right. While I think it is likely that the XP machine is the problem, I have never found a way to prove it.
And I think it is likely the network method that is the problem. I have web server on almost all my computers and I never have problems connecting to them. Two things you might consider. One is to make an FTP connection to transfer the files. I suggest that because it is a different protocol. The other thing is to make the XP folder available to 'Everyone' without a login. That's what I usually do but I don't have any security restrictions since I'm the only on my networks.
And I think it is likely the network method that is the problem. I have web server on almost all my computers and I never have problems connecting to them. Two things you might consider. One is to make an FTP connection to transfer the files. I suggest that because it is a different protocol. The other thing is to make the XP folder available to 'Everyone' without a login. That's what I usually do but I don't have any security restrictions since I'm the only on my networks.
Dave,
I share your situation as you describe: "That's what I usually do but I don't have any security restrictions since I'm the only on my networks." I too am the only one on my network except for my wife, and she barely knows she is on my network. So I don't have much concern about what she is doing. I also share your experience: "It has seemed to me that XP networking doesn't always work quite right." But when I finally figure it out it is usually me that has my head up my ass. And from time to time I don't actually "figure it out". So I just have to be superstitious about it.
I finally figured out a solution to my problem. Looking at the image file that I uploaded to this question, you can see where it says: "Domain: HP003". Since I don't use my basic knowledge about networking very often, from time-to-time I forget what I know. That statement about domain had me thinking I had to connect to my IBM003 machine using credentials from that domain. That was wrong. I still had to connect to IBM003 using credentials that were valid for IBM003. I tried doing that initially, but it failed. The reason it failed was because I was using the UID that I had setup on IBM003 but I was using the PW that is valid for that user of IBM003 when connecting to a server that had Microsoft "Active Directory" on it. I should have been using the PW for the UID that is used when connecting to IBM003 as domain local-host. That way the credentials would have been validated by local-host IBM003 instead of the server with AD on it. I usually keep both PWs the same. But in this case AD wouldn't allow me to use the same PW because it wasn't strong enough. So I had to mutate that PW so it would work with AD. That is why I couldn't connect to IBM003 using the credentials that I was using. When I tried to connect to IBM003 using the credentials that were good for local-host, I was able to connect OK and everything worked as I thought it should in the first place.
I have regretted from time-to-time putting AD on that server. AD only makes sense for enterprise environments. My environment is a long way away from being an enterprise environment. And it is extremely unlikely that it ever will be. I just wanted something to experiment with AD, but it has been mostly a pain in my behind.
But since yours was the only response I got and it got me to pull my head out of my ass and see what I was doing wrong, you deserve the points.
Thank you for your help.
I share your situation as you describe: "That's what I usually do but I don't have any security restrictions since I'm the only on my networks." I too am the only one on my network except for my wife, and she barely knows she is on my network. So I don't have much concern about what she is doing. I also share your experience: "It has seemed to me that XP networking doesn't always work quite right." But when I finally figure it out it is usually me that has my head up my ass. And from time to time I don't actually "figure it out". So I just have to be superstitious about it.
I finally figured out a solution to my problem. Looking at the image file that I uploaded to this question, you can see where it says: "Domain: HP003". Since I don't use my basic knowledge about networking very often, from time-to-time I forget what I know. That statement about domain had me thinking I had to connect to my IBM003 machine using credentials from that domain. That was wrong. I still had to connect to IBM003 using credentials that were valid for IBM003. I tried doing that initially, but it failed. The reason it failed was because I was using the UID that I had setup on IBM003 but I was using the PW that is valid for that user of IBM003 when connecting to a server that had Microsoft "Active Directory" on it. I should have been using the PW for the UID that is used when connecting to IBM003 as domain local-host. That way the credentials would have been validated by local-host IBM003 instead of the server with AD on it. I usually keep both PWs the same. But in this case AD wouldn't allow me to use the same PW because it wasn't strong enough. So I had to mutate that PW so it would work with AD. That is why I couldn't connect to IBM003 using the credentials that I was using. When I tried to connect to IBM003 using the credentials that were good for local-host, I was able to connect OK and everything worked as I thought it should in the first place.
I have regretted from time-to-time putting AD on that server. AD only makes sense for enterprise environments. My environment is a long way away from being an enterprise environment. And it is extremely unlikely that it ever will be. I just wanted something to experiment with AD, but it has been mostly a pain in my behind.
But since yours was the only response I got and it got me to pull my head out of my ass and see what I was doing wrong, you deserve the points.
Thank you for your help.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial