Connect samba share windows xp
Someone tell me it is a firewall problem. Does anyone know how to configure the firewall in order to allow accessing from window to linux?
Jack, Sorry can't help on Linux firewall. Not familliar with that. It shouldn't be installed by default unless you have chosen and setup that up before. First, my experience with RedHat 9 is that it does install the firewall by default, and also configures it for 'high' security.
This, of course, blocks the samba ports. My suggestion is to deal with one thing at a time: disable the firewall for now, and get samba to work the way you want.
However, I'm getting the impression that this is not what you intended. If you change the securiy setting from 'server' to 'share', and comment out the pasword server line, I think you will start to get closer. Then, make sure that there is a system account for the each user that you want to access the samba share. Once, this is all set, you can follow Kay's directions to add users to samba. One note on this: I usually find that it is easiest to make the samba user name match the profile name of the Windows XP user.
The good news is that there's a way around that, but let's not worry about it yet if we don't need to! BTW, since you have the 'domain master' line commented out, you can also comment out the [netlogon] share, as this should only be used when the samba server is acting as a domain controller. Hope I'm not confusing things further! Agreed with Andrew. Recently setup another new machine with Samba.
Couldn't get it start. Linux firewall was set too high when i initially setup the box. So try lower the firewall settings. Same thing could happen on your XP firewall. Make sure the setting is the similar between the 2 files. Well, you get the idea. Boost this thread! How to make Linux access the Windows share folder or access other linux samba? Double click My Network Places icon on your Windows system desktop. If your Samba Server working properly, the windows authentication dialog box should appear on your screen On the Enter Network Password dialog box, key in the Windows Username the Windows Username that you create from 'create samba user procedure' on C onnect As: field, then enter the user password in the P assword: field and then click OK button to proceed.
Samba related article:. Step by step Samba File Server configuration procedure. The example of smb. Keywords: using samba share folder, samba share folder, samba home directory, access samba server, accessing samba folder, samba folder, open samba folder, open samba share, samba folder form windows, samba printer share. Home Contact Us Disclaimer Privacy. Tags: Linux Network. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums.
Answered by:. Archived Forums. Windows 7 Networking. Sign in to vote. Friday, July 27, AM. Try uninstalling KB Sunday, September 2, PM. Take a look at which services are on. I was unable to access samba shares from this windows 7 pc, even its own ones that were accessible from other computers. Friday, July 27, PM.
Thanks Elliot, sounded like a hopeful idea. Thanks for taking time to make the suggestion though. Saturday, July 28, AM. Hi, I have a little confusion about the point 9. Best Regards Scott Xie. Monday, July 30, AM.
Thanks Roy. Hi, Could you please capture upload the network trace on the client side when you reproduce the issue so that I can try to check it? Tuesday, July 31, AM. Thanks for staying with this Scott, I used Wireshark to capture network activity in promiscuous mode while I double clicked in WE on the shared folder under the server in Network.
Best regards, Roy. Hi Roy, OK, please email the logs to v-yexie microsoft. Wednesday, August 1, AM. Have emailed the trace, thanks Scott. Actually two traces and a couple of explanatory images. Also for the record, I re-enabled SMB 2.
Thursday, August 2, AM. Hi Roy, I check the network trace you sent me. Friday, August 3, AM. But I don't think that should affect access to the Linux box, because I use the same account name roy but different password on the Linux machine, and I supply the Linux account password when asked for it by the Linux share. I have double-checked my Windows 7 password, by 'changing' it to the value it already has. As the change requires the existing password before it will accept the 'new' one, and that was accepted, I was able to confirm that there was no error there.
In addition, I have previously tried setting my Windows 7 account password to the same one used in the Linux box so that the account credentials are identical on both machines, but that makes no difference.
I don't use Kerebos or any other pass-through mechanism. And I just tried this again, in case any of the other changes I have made might have got me past the log-jam, but no luck. I have tried two ways of providing the Linux account password: 1. My Linux account normally has access to all five. Thanks and best regards.
Friday, August 3, PM. Hi Ang, I don't know how it was done - it was set up by someone else years ago. Hi Ang, I know it is accessible on the network to all users because all users have access via WinXP and Vista and have had for years, added to which, I have their names and passwords and can try for myself.
This sever has been active for years with XP and Vista clients with no problems. It's only when we got a Win7 machine that access became a problem. If I do the same thing on a Vista box, it opens OK. Saturday, August 4, AM. Monday, August 6, PM. Hi, Ang, Microsoft network client: Digitally sign communications always was already set to Disabled Microsoft network client: Digitally sign communications if client agrees was enabled, and I even tried disabling that and restarting, but it made no difference.
I would have been surprised if it had worked, but still An image showing all my local security policy settings is here. I give them, and then it will show the shared directories, so it considers them valid. Contact the admin I saved copies of the existing smb. Then in smb.
After this, neither Windows 7 nor Vista could access the share - they could see the server, but could not even display the shared directories, and did not ask for credentials. I re-instated the Smb. As usual, a Vista PC could then access the shares, but not Win7. Do you have any other firewall or something that could be affecting it? Something else to try would be I had tried turning Windows Firewall off at a very early stage in my investigations, but I hadn't realized that this wouldn't stop the service immediately, so I just gave it another try.
After stopping the service, the Samba share was still not accessible. On the question of other firewalls, I did originally install an old version of ZoneAlarm, my favorite firewall for XP, but it didn't function as a firewall on Win 7. After installation, I found it just let programs access the network without asking. So I uninstalled that and deleted all its program files.
I did try making a new share on the Linux box yesterday. It appeared and was writeable in Vista and XP Mode, but as with the others it was visible and not accessible from Win7. I have a Fedora server for experiments, and Samba shares on that are accessible, so it seems it must be something to do with the version of Samba, 2.
Tuesday, August 7, AM. Now I am little confused Tuesday, August 7, PM. Well I'm thinking this a problem with samba versions and windows 7 now. I've been following this thread with interest as I have a similar problem.
My home server runs FreeNAS 8. She can see the shares but trying to access them results in "You might not have permission to use this network resource" etc So far I have tried everything suggested in this thread but like the OP nothing is solving the problem This may take a while, but I'll report back for others with the problem.
Wednesday, August 8, AM. I tried adding the keys to registry and removing the entries from the net use table but neither idea worked for me I'm afraid Adding the registry keys did not work for me either. So I followed the route of Ghosting the disk, and installing a later Samba rpm. I settled for samba Unfortunately, I ran into a heap of dependency problems, listed later. By that stage, not suprisingly, no Windows client could see the Linux server, so I ghosted it back and restarted it.
Any suggestions? Friday, August 10, AM. I'll look into installing Fedora in a VM. Do you know if old versions of Linux support VMs? Many thanks for your help. Friday, August 10, PM. Saturday, August 11, AM.
0コメント