General discussion


Windows 2003 Cluster Shares (DFS) & NT4

By gary.medley ·
this is a wierd one :

NT4 client CAN connect while on the LAN to a WIN2K3 box's DFS and normal shares but not when dialled in, or broadband.

The client CAN connect to WIN2K3 shares on another server from both the LAN and dialup.

XP clients can connect to everything from everywhere!

Not sure why the 2003 cluster doesn't like the NT4 client when outside the firewall and yet can connect to other 2k3 shares but not on this particular cluster. I am trying to test connection to another cluster but finding this problem strange.

Great if anyone has any ideas.

ps. there are no ports blocked on the firewall and using SecureRemote. don't think this is the issue though as other clients can connect and also NT4 clients connect to everywhere else apart from this cluster. the cluster is fine from the far...

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to Windows 2003 Cluster Shar ...

Make sure that the NETBIOS ports aren't blocked, even if you think they aren't.

Also, you might be experiencing a WINS resolution issue. Where is the NT 4 client getting its WINS information when it is remote?

Collapse -

by gary.medley In reply to

thanks for respose - name resolution is via a DNS name suffix. there are no wins servers used when remote. i amd going to test wins/hosts file to see if this makes a difference when i get chance, but the DNS suffix works internally (without WINS servers configured).

Collapse -

by MARSHALLCURTIS In reply to Windows 2003 Cluster Shar ...

domain controller that runs Windows Server 2003, these default security settings require that client computers use both server message block (SMB) signing and encryption or signing of secure channel traffic. Clients that run Windows NT 4.0 with SP2 or earlier installed and clients that run Windows 95 do not have SMB packet signing enabled and cannot authenticate to a Windows Server 2003 domain controller.Install Windows NT4 Service Pack 6a, see this link :;en-us;555038

Collapse -

by gary.medley In reply to

thanks for response, but this has nothing to do with authentication - clients do not log in to a windows 2003/2000 AD domain

Collapse -

by CG IT In reply to Windows 2003 Cluster Shar ...

Remote clients have to have rights to gain access regardless of whether network is active directory based or just a simple workgroup setting. The W2003 box local machine security policies, user rights assignments would come into play e.g. control panel/admin tools/local security policy/user rights assignments/access this computer from the network AND deny logon through terminal services. There are other security settings for local machine policy such as disabling the guest account and remote users are considered quests therefore are not allow remote access.

So, we need some more info to troubleshoot. How is the cluster configured? Who does the cluster belong to? e.g. it's own workgroup? a domain?

Collapse -

by CG IT In reply to

in a way the second answer was partially right. There has to be some way the cluster authenticates connections to it. Be it via local machine security policy, a domain policy, a firewall policy,.... some policy that allows who [the remote client] to connect.

Related Discussions

Related Forums