network sharing problems

[therealtalkinggoat]

while tring to access a remote share located on a windows
machine from a windows machine, i get the error:

\\server\remote directory is not accessable. you might
not have permissions to access...

the system can not find message text for message number
0x%1 in the message for %2.

also, sometimes i get the text:
an internal windows 2000 error has occoured.

i have tried to see if this is a connectivity issue, but the host
responds to ping requests. it will not connect with the ip
address, either. it gives the error:
an extended error has occoured.

the user that is tring to access the share has full
controll. i have checked, cleared and reset the security
on it several times. sometimes, however, i can access the
share just fine. it happens without warning. i don't
think that this is a problem with the samba server and
authentication, though. this was happening before i
installed linux and samba as a pdc. there are no error
logs to match this problem in any of the EVENT VIEWERS.
the system appears to be running just fine. does anyone
have an answer for this problem?

if anyone else wants more information, i have posts in microsoft's
newsgroups under
microsoft.public.windowsxp.network_web,
microsoft.public.windowsxp.security_admin,
microsoft.public.windowsxp.general and
microsoft.public.win2000.security

they are all listed under the names chris or chris wooley and were
posted on the 11th and 12th of january 2004

any help here is most appreciated.

 

[1stITMAN]

Which operating sytems are on the two machines.

Example windows 2000 with shared drive\folder.

User needs to exist on windows 2000.
logging on network as administrator through win 98 machine, then that user needs to exist on the windows 2000 machine.

Other wise u cant get access. If both machines are windows 2000, then you can map drive as administrative user to the c$ hidden share. eg \\server\c$

Zaheer Ahmed Iqbal
I.T Systems Support Engineer
Bsc. (Hons).

 

[therealtalkinggoat]

>sometimes, however, i can access the
>share just fine.

this is not a connectivity issue as far as communication goes. the two computers can see each other just file...

>Which operating sytems are on the two machines.

the two machines are xp.

>Example windows 2000 with shared drive\folder.

>User needs to exist on windows 2000.
>logging on network as administrator through win 98 >machine, then that user needs to exist on the windows >2000 machine.

the user that is tring to access the share has full
controll. ie the user is set up as the administrator or
has been given full controll of the share.

>Other wise u cant get access. If both machines are >windows 2000, then you can map drive as administrative >user to the c$ hidden share. eg \\server\c$

i don't want to give the users access to the entire drive, just one protion or one main directory.

keep in mind, this problem is intermitent. it occurs for a couple of minutes, then goes away. anywhere from 10 minutes to three hours can pass before it happens again. i have checked connectivity when the problem seems to be occouring. i can ping the other machines across the network.

 

[therealtalkinggoat]

found the problem typical microsoft crap!!! be sure and read the part where they tell you how to fix it only if you contact them.

Details
Product: Windows Operating System
ID: 537
Source: Security
Version: 5.0
Component: Security Event Log
Symbolic Name: SE_AUDITID_UNSUCCESSFUL_LOGON
Message: Logon Failure:
Reason: An unexpected error occurred during logon
User Name: %1
Domain: %2
Logon Type: %3
Logon Process: %4
Authentication Package: %5
Workstation Name: %6

Explanation
This event record indicates that a logon attempt was made and rejected for some reason other than those covered by explicit audit records in this category.


User Action
The person with administrative rights for the computer should investigate the root cause of this error.


Unnecessary Event ID 537 Entries in the Security Log
View products that this article applies to.
This article was previously published under Q327889
SYMPTOMS
If the "Logon Failure Auditing" local policy is in use on a Windows XP-based computer that is a member of a domain, the following entry may be recorded in the Security event log if you log on to the local computer instead of to the domain:

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537 Date: 7/23/2002
Time: 9:17:42 AM
User: NT AUTHORITY\SYSTEM
Computer: computer name
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: user name
Domain: domain
Logon Type: 11
Logon Process: User32
Authentication Package: Negotiate
Workstation Name: computer name
Status code: 0xC00000BB
Substatus code: 0x0
CAUSE
This problem occurs because Winlogon.exe incorrectly tries a cached logon process for the user who is logging on to the local computer.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows XP service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name Platform SP
-------------------------------------------------------------------------
09-Sep-2002 18:44 5.1.2600.100 968,192 Msgina.dll x86 none
24-Sep-2002 03:47 5.1.2600.1123 968,704 Msgina.dll x86 1
09-Sep-2002 18:44 5.1.2600.100 1,264,128 Msgina.dll IA64 none
08-Sep-2002 22:06 5.1.2600.100 968,192 Wmsgina.dll IA64 none
24-Sep-2002 03:47 5.1.2600.1123 1,265,152 Msgina.dll IA64 1
22-Sep-2002 04:29 5.1.2600.1123 968,704 Wmsgina.dll IA64 1



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The information in this article applies to:
Microsoft Windows XP Home Edition
Microsoft Windows XP Home Edition SP1
Microsoft Windows XP Professional
Microsoft Windows XP Professional SP1