Connect to win7 share

Hi all,
Just got my first mac a few days ago and it has been great, up till now.
I'm having some trouble with file sharing.
I CAN see the mac folders from the PC, but when trying to connect to the PC from the mac, no luck.
In Finder I go to "connect to server..." I write smb://ipofpc, I enter the username and password and I can see a list of all the shares on the PC. When I pick a share and click Ok I get an error message "There was an error connecting to the server. Check the server name or IP address..."
I tried some things I found on the net, but nothing has worked up till now.
Any ideas? I'm lost!
Thank you!

For testing purposes, try
[global]
workgroup = WORKGROUP
server string = wicked yo
netbios name = bigbro
security = share
; the line below is important! If you have permission issues make
; sure the user here is the same as the user of the folder you
; want to share
guest account = franky
username map = /etc/samba/smbusers
name resolve order = hosts wins bcast
wins support = no
[videos]
path = /media/Videos
available = yes
browsable = yes
public = yes
writable = yes
[pictures]
path = /home/franky/Pictures
available = yes
browsable = yes
public = yes
writable = yes
[music]
path = /home/franky/Music
available = yes
browsable = yes
public = yes
writable = yes
[torrents]
path = /home/franky/Torrents
available = yes
browsable = yes
public = yes
writable = yes
Also, disable password enabled sharing in Windows 7. If it works, you can go from there to get password sharing again.

Similar Messages

Unable to connect to Deployment share via the 2012 Update 1 workbench.

Hi Everyone,
This is a tricky one, I've been scratching my head for a few days now. I have a MDT deployment share, which lives on a server, for argument sake, lets call it: MDT-01. Via the Servers MDT Workbench, I can connect to the deployment share just fine, from
any PC, other than my main PC (which is running Windows 8.1), I can connect to the deployment share just fine. If I load the MDT Workbench on my main PC, it just has a deployment share folder with a red cross on it. If I attempt to remove it, it crashes the
MMC, if I try and open the same deployment share it crashes the MMC. If I give the Deployment Share a different share name, it errors and says I can't use an existing deployment share folder.
I used to be able to connect to the share just fine, but since the last couple of days I've not been able to connect.
Further investigation with PowerShell reveals that the console thinks it has a persistent drive, DS001, but the path is blank, as in ''.
Restore-MDTPersistentDrive -verboseVERBOSE: Restoring drive 'DS001' with path ''WARNING: Unable to restore drive DS001.
If I try to remove the Persistent drive, it errors, and if I try to add any new drive to either the same deployment share, or an alternative, it fails.
I can use the New-PSDrive and Remove-PSDrive Powershell commands to create/remove a replicated drive, but that doesn't actually change the Path value in the Get/Restore-MDTPersistantDrive, as they seem to be separate, even though I think they should
be linked.
The Internet has been no help, so I'm asking the Microsoft crew to be helpful, and not just do the usual "This is posted in the wrong place, this question will now be closed... etc, etc!" This is an MDT question, not a Powershell question, I just
need anyone who has indepth MDT knowledge to look at this.
To make clear, this is not a question about a client connecting to the deployment share, that all works fine, and I can update the deployment share fine from any other workbench.
I cannot connect to my deployment share, from my local MMC MDT workbench, as it thinks it already has one, but with a blank path. I've uninstalled, and reinstalled both the MDT, and ADK components on my Local PC, but I still cannot connect to the Share.
My question is this: The files/registry that stores this DS001 path setting is clearly local to my PC, but where is it, I've search the reg, and I've check files, but to no avail, I'm likely to rebuild my PC because of this, but I'd rather not if I can help
it.
Any Ideas people?
P.s. Sorry if this post seems rude, I do appreciate the help, I just don't have time for being messed about, as we're migrating our XP system to 7, and with less than 60 days remaininf, I could do without this... Thanks for understanding. :D

Persistent drives are just a easy way for the MDT console to keep track of the Deployment Shares you like the most (think of it as "pinning" Deployment Shares to the console).
The list of persisted Deployment Shares are per user and stored in the file:
"%AppData%\Microsoft\Microsoft Deployment Toolkit\User.Config"
Mine looks like:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<userSettings>
<MDTProvider>
<setting name="Drive1Name" serializeAs="String">
<value>DS001</value>
</setting>
<setting name="Drive1Path" serializeAs="String">
<value>C:\DeploymentShare</value>
</setting>
<setting name="Drive1Description" serializeAs="String">
<value>MDT Deployment Share</value>
</setting>
</MDTProvider>
</userSettings>
</configuration>
Make sure the Drive Path points to something valid, otherwise, I would delete (rename) the file and let MDT re-create the file.
I hope this answers your question.
Keith Garner - keithga.wordpress.com

Windows 8.1 laptops losing connect to network share

Good Morning,
We have a few laptops that seem to be able to connect to our network file share and then al of a sudden, its unable to find or access this file server. Trying to isolate what the issue could be. I am going through GPO setting to see if something
is misconfiguration. I know with Windows 7 there used to an excel spreadsheet that explained what settings did what for different systems. The logs do not seem to be providing much help.

Neeskokotywak,
If you haven’t already, try connecting to your share by IP address.
If this works and stays connected, it’s almost certainly DNS issues that you’re having.
It’s also worth trying a few commands on the laptops experiencing these issues.
Press your Windows key and X simultaneously and select Command Prompt (Admin).
Make sure to choose the Admin option as you’ll need elevated privileges for some of these commands.
Enter the following commands:
ipconfig/release
ipconfig/renew
ipconfig/flushdns
netsh winsock reset
You didn’t mention what method you were using to connect to your file share but more information on creating a shortcut to your network share can be found on
this webpage. I hope this helps!
Mike
Windows Outreach Team – IT Pro

Unable to connect to file shares on xserve running 10.3.9

I just inherited a client that is running two xserves running 10.3.9. The servers are running workgroup manager/open directory. One server was out of commision due to a hardware issue. Users are divided equally on the two servers. The servers are only running OD and file sharing.
Any users who have their home directories on server A are able to connect to AFP shares fine. Any users who have their home directories on server B cannot connect to the AFP shares. When I look in the Server Admin program it does not have AFP even listed. And if I run disk repair utilities it says "AFP/appletalk listener not enabled because appletalk is off".
How do I turn this on if it is not listed as a check box?

Firefox 4 requires at least OS X 10.5 and an Intel Mac. There is a third party version of Firefox 4 that runs on OS X 10.4/10.5 and PPC Macs, for details see http://www.floodgap.com/software/tenfourfox
If you prefer, you can get the latest version of Firefox 3.6 from http://www.mozilla.com/en-US/firefox/all-older.html
Mozilla are working to prevent Mac users with non-compatible systems from getting the notification about Firefox 4, and also not displaying the "Download Firefox 4" button on http://www.mozilla.com

Windows 7 can't connect to SMB share

Hello, my windows gaming PC won't connect to my shares on my mini server, the server is clean installed just 2 days ago and it worked at first but now it won't even ask for username password it just gives a message that it can't reach the IP address.
I have tried hostname, FQDN and IP and nothing works. but my 2 MacBook Pros have no problem at all, and is maxing the bandwidth of the LAN when transferring files.
I can post a wireshark log if that helps??

Have you tried turning on and off the Filesharing services?
I know sometimes the SMBX portion of OS X Server might crash... so you would have to retart services..

Can't Connect to PC share Error -41

Untill recently I have been able to connect to PC shares (Mac & PC running XP connected to a router) but it has stopped working. PC to Mac is still ok but I'd rather sit at the Mac than the PC...
My method (which has worked for at least 2 years):
In finder Go-Connect to server - enter server address (in my case) smb://192.168.0.2 then click connect. A window pops up "SMB/CIFS File system authentication", click OK, another window pops up "Select the SMB/CIFS shared volume you want to connect to", select the PC share (I have several) & click OK [all ok so far]
Then a window pops up: "Sorry,the operation could not be completed because an unexpected error occurred (Error code -41)."
Can anyone help with what is wron & a fix? What is error -41?
Any help is much appreciated.
Thanks
John

With some further research I have found an answer in a post from a year ago:
http://discussions.apple.com/thread.jspa?messageID=3005537&#3005537
The problem is at the PC end (surprise anyone?) - probably related to Norton Internet Securuty.
The following registry hack fixed the problem:
http://www.michna.com/kb/WxNotEnoughServerStorage.htm
I had to increase the IRPStackSize value to 20.
Hope this helps someone.
Cheers
John

I connected to home share on my ipad iphone and macbook pro now it's asking me to turn on home share on the apple tv but I have no other remote, any ideas?

I connected to home share on my ipad iphone and macbook pro now it's asking me to turn on home share on the apple tv but I have no other remote, any ideas?

Welcome to the Apple Community.
If home sharing isn't enabled on the Apple TV, you will need the aluminium remote that came with it to do so.

Samba Howto: OSX10.5.8, Linux, WinXB, Win7 shares

*Samba Howto: OSX10.5.8, Linux, WinXB, Win7 share*
After several day of research and trial and error i found a solution, so that the Finder of OSX 10.5.8 shows all samba3 shares (irrespective of the operating system) in the left sidebar below the category SHARES.
My local home network consists of an iMac 6.1 (OSX10.5.8), a MacBook 3.1 (OSX10.5.8), a Synology DSXXX (Linux), a VMWare Win7 (testing environment), a VMWare WinXP (testing environment) and Linksys WRT54GL (firmware Tomato 1,27).
On both Mac and the DS209 I don't use the built-in Samba systems!! Instead I use Samba 3.2.15 from macports on both Macs and on my Synology DSXXX I use Samba 3.2.15 from ipkg. On Windows 7 and Windows XP I use the built-in systems.
_Install macports Samba3_
DO NOT ACTIVATE THE BUILT-IN SAMBA!!!
*Important note*: The portfile of samba3 has a bug. Therefore you have to open the portfile (in a text editor) and add tow lines of code (see below). You will find the macport-samba3-portfile under
/opt/local/var/macports/sources/rsync.macports.org/release/ports/net/samba3/Port file
Change the original portfile from
system "installnametool ${changeline} ${destroot}${prefix}/bin/tdbtool"
system "installnametool ${changeline} ${destroot}${prefix}/bin/testparm"
livecheck.type regex
to
system "installnametool ${changeline} ${destroot}${prefix}/bin/tdbtool"
system "installnametool ${changeline} ${destroot}${prefix}/bin/testparm"
+system "installnametool ${changeline} ${destroot}${prefix}/sbin/smbd"+
+system "installnametool ${changeline} ${destroot}${prefix}/sbin/nmbd"+
livecheck.type regex
Afterwards you can install samba3 using the normal macport commands (or Porticus).
_Create a smb.conf_
After the installation create a smb.conf file under /opt/local/etc/samba3. (I will present only the \[global\] section of my smb.conf.)
Note: replace <specification> with specifications of your computer system
--begin smb.conf
\[global\]
workgroup = WORKGROUP
netbios name = <computername, see system-preferences->Filesharing>
server string = <computername, see system-preferences->Filesharing>
hosts allow = 192.XXX.X. localhost
socket options = TCP_NODELAY
\# use my synology ds209 as wins server
wins server = 192.XXX.XXX.XXX
name resolve order = wins lmhosts hosts bcast
\# my imac/macbook never gets local master browser
domain master = no
local master = no
preferred master = no
os level = 0
winbind enum users = yes
winbind enum groups = yes
idmap uid = 10000-110000
idmap gid = 96000-196000
max smbd processes = 10
security = user
map to guest = Bad User
encrypt passwords = yes
passdb backend = smbpasswd
smb passwd file = /opt/local/var/db/smb/smbpasswd
log file = /opt/local/var/log/smb/log.%m
log level = 0
max log size = 50
--end \[global\] sector smb.conf
_Test your samba installation_
Now you can test your samba server running as daemon using the commandline:
/opt/local/sbin/smbd -D
/opt/local/sbin/nmbd -D
Check if your samba server configuration works:
ps -ax | grep smbd
ps -ax | grep nmbd
If the samba server runs well, stop it:
/opt/local/bin/smbcontrol smbd shutdown
/opt/local/bin/smbcontrol nmbd shutdown
_Create LaunchDaemon files_
Build a wrapper file and a LaunchDaemon file in order to start the samba sever automatically at boot time. (I modified the wrapper and plist files from a official macports mysql installation.)
--beginn wrapper script
#!/bin/sh
\# MacPorts generated daemondo support script
\# Init
prefix=/opt/local
\# Start
Start()
/opt/local/sbin/smbd -D
/opt/local/sbin/nmbd -D
\# Stop
Stop()
/opt/local/bin/smbcontrol nmbd shutdown
/opt/local/bin/smbcontrol smbd shutdown
\# Restart
Restart()
Stop
Start
\# Run
Run()
case $1 in
start ) Start ;;
stop ) Stop ;;
restart) Restart ;;
* ) echo "$0: unknown argument: $1";;
esac
\# Run a phase based on the selector
Run $1
--end wrapper script
--beginn LaunchDaemon script
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Debug</key>
<false/>
<key>Label</key>
<string>org.macports.samba3</string>
<key>OnDemand</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/opt/local/bin/daemondo</string>
<string>--label=samba3</string>
<string>--start-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>start</string>
<string>;</string>
<string>--stop-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>stop</string>
<string>;</string>
<string>--restart-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>restart</string>
<string>;</string>
<string>--pid=none</string>
</array>
<key>RunAtLoad</key>
<false/>
</dict>
</plist>
--end LaunchDaemon script
_Install the wrapper and the plist files_
Create a directory using the commandline:
mkdir -p /opt/local/etc/LaunchDaemons/org.macports.samba3/
Save both files in the new created directory.
Call the wrapper script samba3.wrapper.
Call the plist script org.macports.samba3.plist.
Change to the following directory:
cd /Library/LaunchDaemons/
Create a symlink to the samba3 plist script:
ln -s /opt/local/etc/LaunchDaemons/org.macports.samba3/org.macports.samba3.plist
Load the plist file using launchctl on the commandline:
launchctl -w load /Library/LaunchDaemons/org.macports.samba3.plist
Now smbd and nmbd should start at boot time.
_Create a samba WINS server_
*Important note*: ONLY ON SYSTEM IN A LOCAL NETWORK SHOULD BE A WINS SERVER!!
If you don't have a Synology DSXXX try to run one of the OSX10.5.8 system as a WINS server or use a Linux box.
Chance therefore the smb.conf file from above in the following way:
replace <specification> with specification of your computer-system
--begin snb.conf
\[global\]
workgroup = WORKGROUP
netbios name = <computername, see system-preferencies->Filesharing>
server string = <computername, see system-preferencies->Filesharing>
hosts allow = 192.XXX.XXX. localhost
socket options = TCP_NODELAY
local master = no
\# my synology ds209 works as wins server
wins support = yes
name resolve order = wins lmhosts hosts bcast
dns proxy = yes
\# my synology ds209 works as local master browser
domain master = no
local master = yes
preferred master = yes
os level = 65
winbind enum users = yes
winbind enum groups = yes
idmap uid = 10000-110000
idmap gid = 96000-196000
max smbd processes = 10
security = user
map to guest = Bad User
encrypt passwords = yes
passdb backend = smbpasswd
smb passwd file = /opt/etc/samba/smbpasswd
log file = /opt/var/samba/log.%m
log level = 0
max log size = 50
--end \[global\] sector smb.conf
If you have a Synology DSXXX install samba 3.2.15 using ipkg. I won't here explain how you can install ipkg on a DSXXX. You will find a lot of information about this topic in different synology support, wiki and forums sites.
*Important note*: DO NOT ACTIVATE THE BUILT-IN SAMA SYSTEM!!
After you have installed the ipkg samba 3.2.15 on your DSXXX use the smb.conf file above in order
to create a WINS Server on your DSXXX. (Hint: You will find the netbios name and the server string using the Webinterface Disk Station Manager 2.X -> Network -> Servername.)
*Addtional Note 1*: I really think that you can run every linux box as a WINS Server, because the Synology operating system is linux (as far as I know).
*Addtional Note 2*: On my Linksys WRT54GL I use static DHCP for all components of my local network.
*Addtional Note 3*: I Have filled in Router Name (MyRouter), Hostname (MyRouter) and Domain Name (myzone.com) under Router Identification in Tomato 1.27. (Without this I couln't find my Linksys WRT54GL via full qualified domain name.)
Kind regards, maninfo

in laptop pc with arch i have installed somewhat in gnome under System-->administration called "shared folder". Maybe this sort of software override manual configuration in /etc/samba/smb.conf?
Something like that is probably standing in ubuntu as well i suppose..
Last edited by jacopastorius82 (2010-11-03 22:13:53)

[Solved]Cannot connect to Windows Share printer over network.

I'm having trouble connecting to a windows printer via Samba/CUPS.
I've loaded the lp module, but I don't know if I need to load the USB or Parallel ports modules, or both or neither, since this is a network print.
My organization has provided some basic instructions for Mac users. Working off of those, I have a setup with the device URI reading
DeviceURI smb://ksong8:(password)@ucmprint.ucmerced.edu/ucmglobal?waitjob=false
For some reason, the printer reports that it cannot connect to the CIFS share, even though it should be configured correctly.
Even more curiously, I'm able to connect to the share manually with
smbclient //ucmprint.ucmerced.edu/ucmglobal -U ksong8
and then entering my password.
Am I missing something terribly obvious here? I have a sample of logs in debug mode, but they looked okay to me (as well as very verbose), so I won't put them here. I have attached my /etc/cups/printers.conf.
# Printer configuration file for CUPS v1.5.2
# Written by cupsd on 2012-04-02 23:06
# DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
<Printer UCMGlobal>
UUID urn:uuid:56cf696f-e7a6-3859-49ea-fc990df764e9
AuthInfoRequired username,password
Info UC Merced Global Print Spool
Location Kolligian Library
MakeModel Generic PostScript Printer
DeviceURI smb://ksong8:(password)@ucmprint.ucmerced.edu/ucmglobal?waitjob=false
State Idle
StateTime 1333433102
Type 8400972
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
</Printer>
EDIT: Added myself to sys (somehow missed that on the installation) and did some futzing around with the GUI tools. Got some interesting results, but I need to confirm that they work.
Last edited by chipbuster (2012-04-04 04:06:04)

Solved.
As it turns out, either CUPS or Samba does not like having special characters in the password inside of /etc/cups/printers.conf. They should be replaced with "%" and the appropriate ASCII hex code for the symbol.

Can't connect to DFS shares from machines not part of the domain

I'm not sure if this is by design, but we can't connect to DFS shares from machines that are not joined to the domain. We can't even map a drive using credentials of a domain account.
Is that how DFS is supposed to work?

Hi RJO22,
I did some research on this topic, and got a conclusion:
Clients that belong to a workgroup can only access the DFS namespace if the name resolution mechanism that is in place can locally resolve the domain name
https://social.technet.microsoft.com/Forums/windowsserver/en-US/c3214a4c-8088-446c-ba4d-643d5baf87cc/how-to-access-dfs-namespace-from-a-standalone-windows-2003-server
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How do I add Macbook air to my windows network and how do I connect to windows shares from said Macbook?

Finally, I have a "clued in" boss who wanted a Macbook air. I have it, and I can get to the internet by supplying the correct proxy credentials. My issue is trying to connect him to windows shares on my network? I know how to do this cold for adding a PC, But need some 101 on how to take this awesome macbook air and add it to the domain and how to get connected to various shares within my DOMAIN. as well as use network printers (I assume that is pretty easy). . . I should add that I can ping the servers in question, I am just not familiar with how to connect to them via Mac. . .I am sure this is laughably easy, I am the king of making things difficult, I swear!
Thanks for any and all help as usual!!
Dave

Which os do you have?
Check Apple's Knowledge Base for Printer Troubleshooting solutions and suggestions for your particular os.

Does Lion support connecting to SMB shares?

Hi there,
Has anyone else had issues connecting to SMB shares since upgrading to Lion?
I am unable to connect to any previously accessible shares hosted on local Linux or Windows servers.
Thanks,
Bob

For those of you trying to access SMB shares, I found a free and easy solution.
Since a lot of people report they are able to access their NAS using apps other than the Finder itself, I decided to look for a free Lion-compatible File Manager to use instead of Finder.
I have found muCommander ( http://www.mucommander.com/ ) and indeed it works fine. All I did was click on the button highlighted bellow, go to "bonjour services" and select my NAS. It prompted me for my username and password and voilá, it works fine.
I keep Finder for everyday use and just load muCommander when I want to access the NAS. At least now I don't have to start my WinXP VM anymore just to access it.
Hope it helps you all.

Unable to connect to DFS shares

I know it is a known issue in Windows 10, that it is not possible to connect to DFS shares. Can we expect any hotfix for this soon? Because to be able to test Windows 10 in a enterprise, it is essential to be able to connect to a DFS share (at least in
my case :) )

Hi Richard Diphoorn,
From the following news:
As with the last build, you’re getting hot-off-the-presses code which means there are a few issues. We’ll be publishing WU updates shortly to fix the first two, but the remainder will not be fixed for 9879.
•In some cases you may get a black screen when trying to log-in or unlock. The only option is to hold the power button to hard reboot.
•You will be unable to connect to Distributed File System network locations.
•Some systems may see disk growth of 20GB+ due to driver install duplication. On systems with low disk space this can block setup and cause a rollback to the previous build.
•Skype calls will disconnect and Music will stop playing if those apps are minimized.
•There are several known issues with screen sharing with Lync.
There should be newly update released to fix this issue. You can try the newest update which released in 11.24:
https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB3019269
Alex Zhao
TechNet Community Support

Error -6602 while connecting to samba shares.

Hi everyone, i have some problems with samba client on MacOSX 10.5.8, the problem is that it connects to some shares and some not, and I don't know why, please help.
Here is my samba configurations on Ubuntu server, the problem starts after logging as a user kuba with password, it shows Erro -6602. Login and pass are correct, I use them with a parallel desktops windows xp, and it works. Mac is working with other server which stands on PLD Linux. I don't know if it will be usefull but if i can tell you that password doesn't contain any special chars, the only one is undescore char. The same password and user with some additional letters works on PLD.
I can connect to samba shares on this server with smbtree command, if I use
smbclient //server/share -U user with a password authentication it shows a wrong password (but it's correct).
When I delete the valid user definition I can connect to samba, but only with a readonly mode...
[global]
netbios name = ubunteon
server string = ubunteon
workgroup = *********
announce as = NT Server
announce version = 4.9
security = share
encrypt passwords = yes
update encrypted = no
unix password sync = no
smb passwd file = /etc/samba/smbpasswd
logon script = startup.bat
logon drive =
add user script = sudo /usr/sbin/useradd -g smbusers %u
delete user script = sudo /usr/sbin/userdel -r %u
add group script = sudo /usr/sbin/groupadd %g
delete group script = sudo /usr/sbin/groupdel %g
add user to group script = sudo /usr/sbin/usermod -G %g %u
add machine script = sudo /usr/sbin/useradd -g smbmachines -c 'Konto komputera %I' -s /bin/false -d /var/lib/samba/nobody %u
passwd chat debug = no
passwd chat = New*UNIX*password %n\n ReType*new*UNIX*password %n\n passwd:*all*authentication*tokens*updatedsuccess fully*
passwd program = /usr/bin/smbpasswd -L -a %u
nt acl support = no
nt pipe support = yes
map to guest = Bad User
log file = /var/log/samba/log.%m
max log size = 50
log level = 1
os level = 255
domain logons = no
preferred master = yes
domain master = yes
local master = yes
time server = yes
browse list = yes
enhanced browsing = yes
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
winbind enum groups = yes
winbind enum users = yes
winbind use default domain = no
winbind separator = +
unix charset = UTF8
display charset = UTF8
dos charset = CP852
wins support = yes
read raw = yes
write raw = yes
oplocks = no
level2 oplocks = no
max xmit = 65535
getwd cache = yes
dos filetimes = yes
dos filemode = yes
dos filetime resolution = yes
deadtime = 15
default case = lower
preserve case = yes
short preserve case = yes
case sensitive = no
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384 SO_RCVBUF=16384
dns proxy = no
name resolve order = hosts lmhosts wins bcast
guest account = guest
admin users = smbroot
invalid users = root
load printers = yes
printing = cups
printcap name = cups
[www]
comment = Webpages
path = /home/user/public_html
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[devel]
comment = Development Zone
path = /home/user/0-Developement
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[pdfprints]
comment = Development Zone
path = /home/user/PDF
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[home]
comment = Home
path = /home/user
public = no
read only = no
browseable = yes
writeable = yes
valid users = user
[oferty]
comment = Oferty
path = /home/user/public_html/2-Oferty
public = no
read only = no
browseable = yes
writeable = yes
valid users = user
#udostepnienia widziane przez wszystkich
#drukarki
[printers]
comment = Drukarki sieciowe
browseable = no
path = /var/spool/samba
printable = yes
writable = no
create mode = 0700
#drivery do drukarek sieciowych
[print$]
path = /srv/samba/printers
guest ok = yes
browseable = no
read only = yes
write list = smbroot
#katalog domowy
--------------------------------------------------------------

Hi Ramya,
Following checks may help to resolve the issue.
1) Whether Port 21 is open and allowed to connect with FTP.
2) Ping, FTP and telnet possible from PI box to FTP.
3) User mentioned in Communication channel have authorization for read and write on FTP server.
4) FTP ports are open.
5) Firewall setting done properly.

Win10 connection breaks network share (SMB)

I've noticed this little issue since installing Windows 10.
I have a Windows 7 PC which has a shared drive.
I access this drive from my 2 laptops, and 2 media centers.
All is fine, UNTIL I connect to this network share from the Windows 10 laptop.
Once I do this, I can no longer connect to the network share anymore. Always get timeouts.
Thought maybe something was hogging up the allotted 20 connections, but checked fsmgmt.msc, and it shows no connections to my shares after I close out.
The only way to access the network share again, is to reboot the Windows 7 PC.
Again, this ONLY happens after I connect to said share from the Windows 10 laptop.

I'm getting this exact issue as well! as soon as I try and connect to a share on my domain I'm not able to ping any servers from the Win10 machine and i can't ping back.

Connect to win7 share

Similar Messages

Maybe you are looking for