XP 1-way File Sharing Problem

[tansqrx 0]

Well I hope this question has not been asked too many times but I am having problems getting two XP machines to do file sharing. Actually this might not be the run of the mill question as I have already checked everything I know and I am still dead in the water. Here is my setup.Setup:PC1, Win XP, my main computer and the one that most likely has the problemPC2, WinXPBoth computers are connected via a Linksys firewall/router and then connected to the Net via the routerProblem:PC1 is able to see files on PC2 but not vice versa. While on PC2 you can type PC1 address in and the username/password box pops up. When you enter the correct credentials, the box goes away for a moment and then just pops back up like a bad username or password has been entered. I have tried at least 100 times so I am sure it is not a bad username or password. As a side note, the second time the box has PC1/username in the username field just as you would suspect.What I have done:I have lived with this for about a year now but this week I will need to get a printer working on PC2. As I mentioned earlier, PC1 is the main machine and the one that most likely has the problem. I do a lot of programming so I am constantly changing system settings such as stopping services, playing with the registry, and any number of things the average user would never know existed. Below is just a few of the things I have tried.1. The problem is one way, PC1 can still see files on PC2, network OK2. PC1 can ping PC23. PC2 can ping PC14. Both have Internet access5. Both have static IP addresses, 192.168.1.100 and .1016. Both have simple file sharing turned off7. Both must logon via username/password8. Created new accounts on both with Admin privilege to rule out account issues9. Both have File and printer sharing for MS installed10. No firewall issues as I have disabled them both.11. I can do a nbtstat and both computers have a record, PC1 being the master browser12. Everything else seems to be fine except file and print sharing13. Both are on the same workgroupPossible causes:1. Service turned off?, I have enabled everything even close.2. Netbios problem. PC1 and PC2 have the same settings, don’t know how this could affect it. I thought MS went to a different method via port 443 instead of Netbios anyway.3. Advanced security setting changed on PC1?That pretty much describes everything I can think of and if I could think of it I tried it. I still believe it has to do with a service disabled on PC1, possibly the one that is needed to authenticate a remote computer. If you know which service this is let me know.I hope someone can shed light on this situation as I am lost right now. I have worked network support for years and I have not a clue. If you can give me a solution I would greatly appreciate it and then take you out to dinner (25 mi limit, lol).

[yordan 10]

How do you do the filesystem and printing sharing ? On hostname or on IP addresses ? Did you try with the addresses ?for instance, if you want to use the printer which is on the computer 192.168.1.100, on the other computer click onRun --> Execute -------> \\192.168.1.100\then let the program run, and then you should see a window opening, with all the shared folders and printers, click on the printer, accept thre printer installation, and things should work ok.Regards Yordan

[evion 0]

I had the same problem before though my uncle came in to help me out. All i know about it is that the reason why the other computer couldn't detect the printer is because the printer uses ITX protocol which is another "supported" protocol of windows rarely used nowadays. Not sure how my uncle fixed the one-way file sharing problem i had at first though, he told me its sorta because the 2 computers have different default network settings altogether so they won't work at all.

[tansqrx 0]

How do you do the filesystem and printing sharing ? On hostname or on IP addresses ? Did you try with the addresses ?for instance, if you want to use the printer which is on the computer 192.168.1.100, on the other computer click on
Run
--> Execute
-------> \\192.168.1.100\

then let the program run, and then you should see a window opening, with all the shared folders and printers, click on the printer, accept thre printer installation, and things should work ok.
Regards
Yordan

Yes I alway do all my references by address. When I type \\192.168.1.100 from run, the password prompt box pops up, so that one is ruled out. Thank anyway. Keep the comments comming!

[yordan 10]

When I type \\192.168.1.100 from run, the password prompt box pops up, so that one is ruled out.

This password box seems indicating that the user names/passwords are not the same on both computers. Which user is connected on each computer ? If you are connected as Administrator on computer 2, you must give computer 1 Administrator's password when prompted. If you are connected as "James" on computer 2, a user named James must exist on computer 1, if possible with the same password, else give computer 1 Jame's password when prompted.

[Grafitti 0]

You have waay more experience than me, if you've been doing this for a good while. This may sound stupid, but when i ran into this problem, i just ran the network setup wizard on both computers, and it started working again. it happened when i had bought new computers and was trying to network them, and when one couldn't file share, i would run the wizard and somehow it cleared up the problem.

[tansqrx 0]

Yes I am typing a admin username/password. I have even created new admin accounts on both computers to test out any account problems. As a side note, when I connect I type //192.168.1.100/c$ so there should not be any folder permission problems as long as I use an admin account. Good suggestion, next!

This password box seems indicating that the user names/passwords are not the same on both computers. Which user is connected on each computer ? If you are connected as Administrator on computer 2, you must give computer 1 Administrator's password when prompted. If you are connected as "James" on computer 2, a user named James must exist on computer 1, if possible with the same password, else give computer 1 Jame's password when prompted.

[yordan 10]

As a side note, when I connect I type //192.168.1.100/c$

No, no, no, you should not !
If you want to connect to the printer, you should type \\192.168.1.100\ and not with the c$.
first of all, it's with a \\ and not a //, this could be cause of error.
secondly, connecting to c$ is now forbidden. c$ means connecting without any sharing control, so now it's usually not possible except if you shared c:\, which is probably not the case.
So, you should really try to use the following sequence :
Start -->Run --> \\192.168.1.100\
then you should see each shared folder or printer, and choose the printer.
If you see nothing appearing, then the Windows printer is not shared.


Regards

Yordan

[tansqrx 0]

Ok I need an answer to this question so I will make things interesting. I said I would take you out to dinner if you answered my networking problem, now I am serious. I can’t actually take you out but I will buy it for you. If you provide a solution that directly solves my problem I will send you $25 USD via PalPay. That should be enough for a semi-nice dinner. I’m guessing that such an offer has never been tried here and therefore does not break any Xisto rules, yet. If it does, let me know and I will resend my offer, otherwise let the games begin.Grafitti,I ran the network wizard on both machine and nothing changed. After the wizard the workgroups on both machines is now MSHOME.Yordan,OK I goofed in using the wrong slashed in my reply. I actually use \\. If I did not I would get an error and not the username/password prompt. At this point it is just as important to get file sharing going as the printer. File sharing and printing are so closely related that if file sharing does not work then printing will not either. The way the system is setup, you will have to enter in a username and password to get access to the printer anyway and that is where the problem is.To iterate, my problem is with authentication to PC1. I can ping, FTP, everything else except use the built in windows file/print sharing. After typing \\192.168.1.100\c$ a username/password prompt appears. I type the correct username and password in and the box only reappears.Now get out there and earn your dinner!

[WeaponX 0]

The only thing that I can think of now is the permissions. You didn't mention (unless I missed it) what version XP you are using? If Pro, that might be the problem. I had a similar case like this before when it was stubborn to grant permissions to share files and print to another computer.

You probably did most of these steps already, but download the Word file by Microsoft. Open it up and go to Page 15. Start reading from there and see if those suggestions work. If not, we'll try the permissions (assuming you are using XP Pro) on Page 18.

[yordan 10]

After typing \\192.168.1.100\c$

And I firmly say : don't try to attach c$, you will add standard securities and anti-hacking issues, simply try to run \\192.168.1.100\ without the c$.
Also another way is the box "look for a computer", type 192.168.1.100 and you should see the printer. Except if file and priter sharing is not enabled in XP.
And, of course, the $250 is very attractive. However, I'm pretty sure a lot of experienced young guys will be able to simply directly sit down in front of your computer and solve your problem for five times less money. And if I was closer to your door, I would probably have solved this issue in less time than spent typing here.

Ok I need an answer to this question so I will make things interesting.

No need for extra items in order to make things interesting. All of us are interested in knowing how long we will need to guess what really happens, and who will finally get the solution.
By the way, please tell us when you finished reading the MS-Word document, and the things around page 18 suggested by WeaponX. If three people cannont get a Crosoft printer to work, it's really too bad.
Edited March 1, 2006 by yordan (see edit history)

[tansqrx 0]

Looks like I will be eating that steak dinner alone this time. Congratulations to myself for figuring out the problems (8 hours later and 78 reboots). I almost lost it when I saw yordan’s reply.

 

And, of course, the $250 is very attractive. However, I'm pretty sure a lot of experienced young guys will be able to simply directly sit down in front of your computer and solve your problem for five times less money. And if I was closer to your door, I would probably have solved this issue in less time than spent typing here.

Wow $250, I didn’t think I was that generous. I had a sigh of relief when I saw it was a typo on his part and not mine. I hate to say it but I don’t think anyone even got close to the solution. The problem was about 2 levels beyond the offered solutions. I hope I’m not sounding too nasty, I guess that’s what hours of pounding your head against the desk will do for you. Now without further ado, the solution.

 

“Network security: LAN Manager authentication level” was set to “Send NTLMv2 response only\refuse LM & NTLM” when is should have been set to “Send LM & NTLM responses”

 

I most likely did it to myself while messing around with the Windows security settings about 6 months ago when I reformatted. After a reformat I always harden my box by disabling the Guest account, setting restrict anonymous to 2, deleting Everyone from the default file permissions, and about 500 other absolutely necessary items. These are all things that everyone should do or at least look into. I don’t remember changing that particular setting but a comparison with another machine showed that the default is “Send LM & NTLM responses”. Apparently PC2 was not setup to send a NTLMv2 hash and so when the request hit PC1, PC1 simply ignored it. I had suspicions that the problem had something to do with SMB or something in the authentication as everything else worked fine.

 

This is how you get to this setting. As I said earlier, everyone should at least take a peek at these settings. From the control panel, select Administrative Tools and then Local Security Policy. Many settings can be found here, specifically: Security Settings>Local Policies>Security Options> Network security: LAN Manager authentication level.

 

Let me know if this helped anyone else, and your comments, or revisions to previous solutions. Maybe next time someone will actually get that steak dinner. Always remember that if I end up asking a computer question you should be assured that it is not the average run of the mill question.

[yordan 10]

After a reformat I always harden my box by disabling the Guest account, setting restrict anonymous to 2, deleting Everyone from the default file permissions, and about 500 other absolutely necessary items.

OK, that's the reason why.
I thought that you had the problem immediately after Windows installation. And I thought that everybody did things just like me.
When I come to a brand new set of systems, I
1) format
2) Install Windows
3) get internal PC communcations to work (inside my own network).
4) Install printers, shared folders.
5) test printers, shared folders.
6) Install antivirus
7) install firewall
8) verify that printers and shared folders and telnet and ftp and vnc still work, else re-touch firewall settings
9) configure Internet Explorer (namely default gateway and proxy).
10) Download Microsoft latest updates.
11) harden the box like you suggest.
12) re-test everything.

So, when I saw your post, I thought that you were at step 4. And you were at step 12. That's why I did not really understand what you did.
So, I must correct everything.
If I really came to your home in order to correct this printer thing, it would have lasted far more that five minutes because I would have had to backup your system disk to DVD, and redo steps 1 to 4, which would have lasted at least one hour.

And, yes, sorry, you said

I will send you $25

And I have seen 250 because you were explaining that you wanted to make the things interesting, and I know very few places where two people can have a nice dinner for $25.
Nevertheless, we are happy to see that everything works fine now on your two computers. And, yes, you can be proud because you found the solution by yourself, (almost) without needing help.

[tansqrx 0]

I have to absloutly disagree, you can go to Steak Out and have the best steak dinner all for under $25. Yea sorry for sounding nasty last night, it was a case of lack of sleep. I really didn't want to reformat as I have everything the way I want it and it is alway a pain to set everything back up, esp. all the application settings. It would have taken longer to get everything back up then it took to find the problem. Thanks again for your help.

[Grafitti 0]

You definitely earned that steak, and I can't say I was anywhere near that. But I definitely learned something new from you.