Windows Server 2012 & 2000 Network HELP

Are these on the same domain?

Have you gone through the normal procedures to create a share on the 2012 server and given rights only to Administrator?

See if you can use NTLM Authentication on Server 2000

See: http://support.microsoft.com/kb/239869

Set LMCompatibility to 1

Excerpt from the above support article

To enable a Windows 95, Windows 98, or Windows 98 Second Edition client for NTLM 2 authentication, install the Directory Services Client.

To enable a modern 64-bit system to connect to the above guests, activate NTLM 2 on the host machine, follow these steps:
1. Start Registry Editor (Regedit.exe) on the host machine.
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
3. Create a new DWORD (32-bit) Value under LSA registry key as shown in step 4.
On the Edit menu, click New DWORD (32-bit) Value as follows:
Value Name: LMCompatibility
Data Type: REG_DWORD
Value: 1 (for legacy systems)

I have used this for older workstation but not servers. So you can try it and see if it allows you to see from Server 2000 to Server 2012.  

The gap is pretty wide and you may be stuck with mapping from Server 2012 to Server 2000.

If you have Admin rights on the 2012 R2 server you do not need to create a share, you can use the Admin$ shares for example

\\server1\c$

Select allOpen in new window

Shaun Vermaak - How do I do this exactly?

Start Run
Type and press ENTER

\\ServerName\C$

Select allOpen in new window

Have you tried NTLM modifications on either server yet?

John Hurst - how do I do this?

Use my first description here describing NTLM authorization in detail.

I created a shared drive on Windows Server 2012 but in Windows Server 2000, I need to manually go to "My Network Places" and go to Windows Server 2012 to login before I can access the shared folder.  

How can I bypass this manual login, which appears everytime Windows Server 2000 is rebooted?

You can try a script that contains the user name and password. That should work. It lacks security but if the servers are otherwise controlled, it should be OK.

John Hurst - I haven't done this before.  Is there a sample script with user name and password that would do this auto login when Windows Server 2000 reboots so this machine has access to the shared folder on Windows Server 2012?

Try NET USE X: \\Server\C$ /user:DOMAIN\username password. As noted, it is not secure but there are simple huge differences between Server 2012 and 2000.

Or this if not on domain

NET USE /netonly X: \\Server\C$ /user:ServerName\username password

Select allOpen in new window

John Hurst & Shaun Vemaak

1) What is the value of X?
2) Are "Server" and "ServerName" the name of the Server 2012 or 2000 machine?
3) Would this script be on Server 2012 or 2000?  Is it a .bat file that I would run as a Scheduled Task when the machine starts up?

"X" is just a drive letter. Use Z, T or whatever.

In your example, first post, Server (ServeName) is the name of Server 2012 because you are doing this on the Server 2000 machine.

The script would be a .BAT file on the Server 2000 machine. You could try it as a scheduled task of course.

John Hurst:

RE: NET USE X: \\Server\C$ /user:DOMAIN\username password

What is "C$" and "DOMAIN"?

How can I see the DOMAIN value from Windows Server 2000 or 2012?

I used the following in a .bat file but it didn't work:
NET USE X: \\Server2012Name\C$ /user:DOMAIN\Server2012Username Server2012Password

Where:
X - drive latter to map to
Server2012Name  - my Server 2012 computer name
Server2012Username  - my Server 2012 login
Server2012Password - my Server 2012 password

C$ is the root folder

DOMAIN is the name of the Server 2012 domain

Domain can be seen in Computer, right click, Properties, Name.

RE: Domain can be seen in Computer, right click, Properties, Name.

I can see computer name, full computer name, computer description, and workgroup.  I don't see Domain here.

If your computers are not on a domain , then perhaps map by IP address.

RE: NET USE X: \\Server\C$ /user:DOMAIN\username password

What syntax do I use above to map by IP address?

If there is no domain (you should know if there is or isn't as most servers are a domain), then use the workgroup form

NET USE X: \\ip_address_of_server_2012\folder_to_be_mapped  and enter and authenticate.

And by the way, it will be MUCH easier to map a Server 2000 folder from Server 2012 rather than the other way around.

RE: it will be MUCH easier to map a Server 2000 folder from Server 2012 rather than the other way around.
I don't know how to do this.  I can't see Server 2000 from Server 2012, but I can see Server 2012 from Server 2000.

RE: NET USE X: \\ip_address_of_server_2012\folder_to_be_mapped  and enter and authenticate.

I did this ... NET USE X: \\ip_address_of_server_2012\folder_to_be_mapped and save it as MapServer.bat

I clicked on the bat file and it didn't work.  How can I authenticate inside the bat file?

Open cmd.exe and then in the command window type: NET USE X: \\ip_address_of_server_2012\folder_to_be_mapped  and enter.

What error number did you get ?

RE: Open cmd.exe and then in the command window type: NET USE X: \\ip_address_of_server_2012\folder_to_be_mapped  and enter.
The syntax of the command is incorrect.  See http://prntscr.com/eszdya

You have to change my "names" to IP addresses. You cannot type in a placeholder and expect it to work.

I am beginning to thing you do not have a good understand of sharing folders. So why be bothered with an ancient system to test on.

Perhaps read my folder sharing article in depth,

https://www.experts-exchange.com/articles/16639/Folder-sharing-on-modern-machines.html

I am able to MANUALLY connect to the Shared Folder on Window Server 2012, but I have to enter the user login and password.

If a bat file with the correct syntax AUTOMATICALLY loads when Windows Server 2000 is started / rebooted, that would eliminate this manual login process.

I tried using the syntax of your command using computer name and or IP address, but I am still getting syntax errors.

Please help.

RE: NET USE X: \\Server\C$ /user:DOMAIN\username password
If you check the output of: net use /? you should note that the password goes before the username part:
NET USE X: \\Server\C$ password /user:DOMAIN\username

! am able to MANUALLY connect to the Shared Folder on Window Server 2012   <-- Progress!

NET USE X: \\server\folder /user:domain\username password.

Server is your server name.
Folder is the folder you want to map
domain is the Domain of your server 2012 and may be optional
user is the username
password is the password.

Make your batch file from the command that worked and add the username and password to it.

Open a command window and run the batch file in the command window to see what it does.

I followed your syntax, but it gives an error ... The option /MyUserName is unknown.  

MyUserName is the username I used to access the shared folder on WIndows Server 2012.  See http://prntscr.com/et9uz8

/User:username password

RE:
NET USE X: \\server\folder /User:username password.

I am getting the same syntax error.

Please post the exact command string you used to log on manually. Don't post an actual password

Shouldn't the password go before the /user:username and not after?

I put it after; I think it can go before as well.

Syntax (from the horse's mouth)

NET USE  
[devicename | *] [\\computername\sharename[\volume] [password | *]]
        [/USER:[domainname\]username]
        [/USER:[dotted domain name\]username]
        [/USER:[username@dotted domain name]

Please post the exact command you used to log in manually.

I haven't tried putting it after, though I could imagine that it works.

The "horse's mouth" specifies the password as being before the /USER.... part.

The servers don't have a domain name.  I am getting the same syntax error using:

NET USE X: \\Server-g98efxesgsw\TestSharedFolder PASSWORD /USER:adminuser213@189.132.115.33

If "adminuser213" is a user on "Server-g98efxegsw" then try:
NET USE X: \\Server-g98efxesgsw\TestSharedFolder PASSWORD /USER:adminuser213@Server-g98efxesgsw

It may be the way Server 2000 does its user / password syntax doesn't match Server 2012

However you are able log on and map a drive which was your question here originally.

John Hurst - The shared folder needs to be automatically accessible when Windows 2000 restarts.   What is the syntax for Server 2000?

CompProbSolv - RE: If "adminuser213" is a user on "Server-g98efxegsw" then try:
NET USE X: \\Server-g98efxesgsw\TestSharedFolder PASSWORD /USER:adminuser213@Server-g98efxesgsw
I am still getting a syntax error.

On Server 2000, open a Command Prompt and type NET USE /? and enter to get help.

My point was the way Server 2000 passes the parameters may nut be recognized by Server 2012.

"The servers don't have a domain name."
To be clear about this, are you saying that Active Directory is not set up or, if it is, you do not want to use this for this login?

Also, if you go to a CMD prompt and type:
NET USE X: \\Server-g98efxesgsw\TestSharedFolder
you should get a prompt for user name and password.
If you type: adminuser213@Server-g98efxesgsw
for the user name
and you type: PASSWORD
(actually, whatever the real password is)
for the password, does it properly map the drive?

I don't think Active Directory is set up.  How can I check in Windows Server 2000?

RE: Also, if you go to a CMD prompt and type:  NET USE X: \\Server-g98efxesgsw\TestSharedFolder
you should get a prompt for user name and password.

I am getting the same syntax error.  See http://prntscr.com/eu3pvq

Use NET USE /?

and get help for your syntax and see if you made errors. I don't think so and so I think Server 2012 is simply not going to understand Server 2000 parameters

"I am getting the same syntax error.  See http://prntscr.com/eu3pvq"

The screenshot doesn't show exactly what you typed for the command.  Please include a screenshot that shows it and the results.

Agree.

Once again "Please post the exact command you used to log in manually"

I typed in exactly:

NET USE X: \\Server-g98efxesgsw\TestSharedFolder

From my own Windows 2000 machine.

NET USE [devicename | *] [\\computername\sharename[\volume] [password | *]]
        [/USER:[domainname\]username]
        [/USER:[dotted domain name\]username]
        [/USER:[username@dotted domain name]
        [[/DELETE] | [/PERSISTENT:{YES | NO}]]

The syntax purports to be the same, but since it does not work in a batch, the preparation of parameters in Server 2000 does not work for Server 2012.

This means it is not going to work - ever. So you must log on manually.

I don't have a working Server 2000 system at the moment.  I'm quite perplexed as to how you would get the response that you showed in the previous screen capture. It would be a bit clearer if we had the screenshot with the command AND the output.

The screenshot implied that you had something wrong with the syntax and not with the specifics.  That is, if "Server-g98efxesgsw" were not a valid name, you should have gotten a response to that effect.

It's also important to note that this is not specifically a .BAT file problem.  As I'm reading these (many!) posts, the problem exists at a CMD prompt without consideration of .BAT files.  If you can't get it to work when typing it out on the CMD line, you'll not get it working in a .BAT file!

CompProbSolv - Server-g98efxesgsw is a valid name and I used the command prompt.  You're right it's not a .BAT file problem because it doesn't work when typing it out on the CMD line.

John Hurst - RE: The syntax purports to be the same, but since it does not work in a batch, the preparation of parameters in Server 2000 does not work for Server 2012. This means it is not going to work - ever. So you must log on manually.
Yes it works only if I log on manually ... which doesn't make sense unfortunately.

"Server-g98efxesgsw is a valid name and I used the command prompt. "
As mentioned, a screenshot with your command and the response may help here.  Otherwise, I don't think you'll get anything else constructive here.

Thank you John!

You are most welcome. Sorry that you must use manual login, but at least you can connect the devices.

I was happy to help you out.