Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi
I have an access control system that runs on a DOS machine, using Microsoft Network Client 3.0 to connect to an NT4 server (DOS client uses TCP/IP, maps a network drive that it uses to check for updated data files) This system has worked fine for years - until I upgraded the server from NT to Server 2003. Now when the DOS client boots, it connects to the server fine (connects a G: drive to a share on the server) but even if I log on as administrator when I try & do anything on the network drive I get access denied errors. The administrator has access to the share I am connected to, & works fine if I connect from a windows client - & when I try to connect to a share on ANY other operating system (2000, 2000 server, XP pro, NT4, NT4 server, etc) anyone have any idea why Network Client 3.0 won't connect to server 2003 shares?
Thanks

Do you have both the Client and Server setup in DOS ??:
http://www.wown.com/j_helmig/dosclien.htm
and are mapping the DOS share in W2K3 COMMAND PROMPT ??:
net use * \\computername\sharename

Ok Chap...
Problem you've got is settings on your Default Domain Controller policy. Set
up the following in the policy (computer config\windows settings\security
settings\local policies\security options)Microsoft network server: Digitally sign communications (always) is set to
Disabled - note not defined will not work.
Microsoft network server: Digitally sign communications (if client agrees)
is set to EnabledThis will however leave you open to possible man in the middle attacks so
make sure you understand all the security implications before you go ahead.Have fun.....

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |