Need to access Windows 2000 server

[mlee1steph]

Hi
I'm having a problem setting up my Windows 2000 server machine so that I can have access from a Windows XP Home system (my main system). I have setup a user on both machines and still can't get access to the drive on the 2000 machine. I have 3 machines connected to a router that give us access to the internet. The windows 2000 machines (2 0f them) are both running Windows 2000 server, but they are being used as a server. What can I do from here. Are there any good How-To's on this setup? Thanks for any advice.
Michael

 

[wolluf]

Are the machines all in the same workgroup? (XP home can't belong to a domain of course). What exactly is happening when you try to access the 2k shared drive from XP Home machine? How are you trying to access it (eg, \\servername\sharename in run box?) Do you have any firewalls enabled?

 

[mlee1steph]

Thanks for the reply. Right now I'm working on getting one of the 2000 machines working which is running the Pro version. When I was trying to use the default user Id of the XP machine, I could see the printer sharing just fine, although I never tried to print to the printer. But then I created a userid on the XP machine (user2) that already excisted on the 2000 machine. When I try to connect to the shared directory now, the first time it asked for a userid/password. I entered the info and after clicking OK the logon dialog came back, as if I was entering something wrong (no error message at this point). After several tries I closed the login dialog. Now if I try to access the shared dir I get the following error message:
\\Flag\Shared is not accessible. You might not have permission to use the network resource. ect......
If I look under the "Printer and Faxes" area the printer that was once on the 2000 machine is viewable from the XP machine, so it has some type of connection to the 2000 machine.
Both machines are also running NTFS. The 2000 machines are not setup in a Domain. I've check for that also. I do have the XP firewall, but would that cause me not to be able to connect to the 2000 machines? I hope this helps. Thanks again for the reply.
Michael

 

[mlee1steph]

This is where I stand as of now. Late last night, I decided
to install XP Pro on the 2000 machine I was trying to connect to. But I still can't access the shared directories. I currently have two user ID's on each machine. One does not have a password, but the other does. When I Open "Microsoft Windows Network" I see the other computer within the workgroup. If I try and click on the Other computer I get the following error now:

\\Mike is not accessible. You might not have permission to use this network resource. ect....
Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been renforced.

Also I used to be able to see the Printers on the other computer, but I don't seem to see that now. How do I check see if a blank password is allowed? I'm still doing research to fix the problem, I think I may have something set wrong, either with the user accounts or the XP firewall on both machines. Does the XP Filewall block access to each other, even if there on the same workgroup? If so. How do I change that. Thanks for any info.
Michael

 

[MysteryFCM]

Yes it does. On my network atleast, internal machine communication occurs on port 445 (SMB) so you'll need to ensure that is open (on and for the INTERNAL machines only of course, not on the router).

Because the machines are not part a domain, you don't need to setup specific usernames.

Regards

Steven Burn
Ur I.T. Mate Group

http://www.it-mate.co.uk

 

[mlee1steph]

I finally got it to work. I finally got access to the drive, but could not copy the file over to the other computer. But I found that if I select "Simple Printer and File Sharing" and I created a dir outside of the "Documents and Settings" dir, I then was able to copy the files over. So things are looking better, now I'm working on getting to work the other way, but I'll do that later. Thanks again for all the help.
Michael