Tag: samba

[Solved] – Network Location in no longer available or Error 59 on Windows XP system

You may have gotten a pop up on Windows that says your network resource is no longer available after a password change or password expired notice and while using Network Neighborhood. During troubleshooting you find that others can access share, the server is pingable but you can not access any share on system and it feels like XP thinks the server is not there.

I have found that this was caused by Windows Credentials being stored in the system and that the credentials  were not correct.    This issue happens in both Windows 7 and XP.

In order to fix something like this you will need to go into the Windows Credential Manager and remove the stored password.

 

To do this:

 

Windows 7: Control Panel – Windows Credential Manager

Windows XP – User Accounts – Username – Stored Network Passwords (Top left link)

 

 

Once removed retry to access share, you should now see share respond and pop up a user password windows. Place in the correct credentials and you’re in.

 

 

I hope this helps someone out there..

 

Cubert  😎

\NETLOGON fnum 0x8007 returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED

Samba and Winbind Fix for Windows 2008 R2 Active Directory Services

Having issues with file sharing when inside a Windows 2008 R2 Domain? Are you getting these errors in you logs?
rpc_client/cli_pipe.c:rpc_api_pipe(790)
rpc_api_pipe: Remote machine 0.0.0.0 pipe \NETLOGON fnum 0x8007 returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
A little searching online shows a lot of people with this or related problems, It looks like there’s a bug in the samba package that prevents

Samba and Winbind Fix for Windows 2008 R2 Active Directory Services

Having issues with file sharing when inside a Windows 2008 R2 Domain? Are you getting these errors in you logs?

rpc_client/cli_pipe.c:rpc_api_pipe(790)
rpc_api_pipe: Remote machine 0.0.0.0 pipe \NETLOGON fnum 0x8007 returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED

A little searching online shows a lot of people with this or related problems, It looks like there’s a bug in the samba package that prevents it from working with Windows Server 2008 R2 domains. If you’re running into this problem, the solution is to remove your existing samba installation and install, instead, the samba3x packages.

Run the following on your Redhat or CentOS installation.

yum erase samba samba-common
yum install samba3x samba3x-client

You will need to rebuild your connections to AD via winbind and rebuild your SMB.conf so I would suggest you save your files before starting the process.

If you need help rebuilding Winbind and Samba this web post is a great example how to do it.

http://www.sweetnam.eu/index.php/Using_Active_Directory_for_CentOS

Enjoy.

P.s

When joining server to AD (step #9) in web post

 net ads join -U administrator@SWEETNAM.EU

It seems to join correctly if you just use “admin username” with out the @domain added to the line. It always seems to fail if I use the entire domain name in the join request. Instead I use the following example and it works great for me.

net ads join -U administrator

Good Luck

Cubert