SMB share problems...

jlazzaro

Golden Member
May 6, 2004
1,743
0
0
We have 30+ Server 2003 Enterprise machines, however one of the servers is giving me an issue (well call it Server1)

All XP clients can access every server via simple shares (\\server\c$), even Server1

All Servers can access XP clients via simple shares (\\client\c$)

Server1 can access every other 2003 Server, but no 2003 Servers can access Server1.

When connecting to Server1 from any 2003 Box, a bad username/password error is given.

This is using the same username/password that is successful from an XP machine. Any ideas?

LOGS:
Failed authentication from a 2003 box to Server1:

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: admin_acct
Source Workstation: Server2
Error Code: 0xC000006A

Logon Failure:
Reason: Unknown user name or bad password
User Name: admin_acct
Domain: Server1
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: Server2
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: x.x.x.x
Source Port: 0


Successful authentication from an XP machine to Server1:

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: admin_acct
Source Workstation: Client1
Error Code: 0x0

Special privileges assigned to new logon:
User Name: admin_acct
Domain: Server1
Logon ID: (0x0,0x85C6F)
Privileges: SeBackupPrivilege
SeRestorePrivilege
SeChangeNotifyPrivilege

Successful Network Logon:
User Name: admin_acct
Domain: Server1
Logon ID: (0x0,0x85C6F)
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: Client1
Logon GUID: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: x.x.x.x
Source Port: 0


I don't understand how one authentication is successful and the other fails, even though both are using the same credentials.

 

vorgusa

Senior member
Apr 5, 2005
244
0
0
I did not thoroughly read through all that but it could be a networking problem.. are the servers in a different area on the network from everything else.. you might just have a firewall blocking the connection... try moving one of the computers that can not connect to a switch or router that is connected to a computer that can connect to server1