Windows file sharing across subnets

I have a SonicWall TZ170 wireless router that will not allow the LAN and WLAN to have the same subnet IP address. I have a WinXP Pro desktop on the LAN at 192.168.70.100 and a PowerBook on the WLAN at 192.168.71.100. The router firewall is set up to allow all traffic (any IP address) between the two subnets. However, no matter what i do, I cannot get the PowerBook to connect to the PC. (I've also tried SMB://192.168.70.100/share, where "share" is the name of the shared folder on the PC.) I know the file sharing settings are correct, since I can mount the PC share when the PowerBook is connected to the LAN.
I've since read that SMB does not work over different subnets. Is this correct? If so, is there any other way to share files on the PC with the PowerBook?
PowerBook G4 15 Mac OS X (10.4.8)

Ideas?
I'm downloading the manuals, to see if I can glean any clues from there as far as configuring the firewall rules in the device.
I suggest that you do the same.
http://www.sonicwall.com/us/support/3134.html
There are several product guides and how-to PDF's...
The other idea that might work would be to follow their suggestion: "Specifics at this point are probably best dealt with in the form of a call to our technical support team."
this is looking less like a mac issue and more like a SonicWall issue.

Similar Messages

Novice to setting up Windows file sharing in order to connect with macbook

Hi everyone,
I have been having major trouble trying to set up my Dell laptop to set up windows file sharing with my macbook pro (just got it yesterday). I am not very technically savvy, but I did enable that my C folder be shared on the network, so when I go to network places, it shows up.
I currently have my mac and dell connected by a cat 5 cable, so they are directly connected to each other. However, I have no idea where to go from here! I have read many support sites and pages, but it doesn't make sense to me. I need a watered down version of how to make my hard drive a server.
I also enabled file sharing on my mac , which was simple, but i am confused if i even need to do that.
Thanks in advance for any help. It will be GREATLY appreciated!!

1) You aren't using a router or BaseStation in this little network?
2) If not, you will need to set IP addresses manually. Otherwise you'll have a connection, but no data flow.
3) Your shared drive on the Dell will show up in Neighborhood on the Dell. that's normal.
BD- Have you seen a good tutorial for this?
PS, Amanda - sharing out your entire "C" drive is not a good idea. Once we get you networked...it will be possible for the mac to delete a folder that's inside the Dell's "C" drive. Could be a system folder that you blast...there is no RecycleBin when you delete files across a network.
Don't mean to scare ya, just showing you the possibilities.

Windows file sharing can no longer work after tiger upgrade

hi guys, ive been searching the web to find a cure on my problem for a long time now, but still no success, hope someone could help me out.
ok heres my problem, before the upgrade, file sharing with windows is perfect, with no problems at all, but when i upgraded one of our mac to tiger, windows file sharing is not working anymore, i cant connect or see my windows xp computer on the network and vice versa, windows cannot see my mac with tiger on the network.
Our other 2 macs here running in panther are fine( meaning, windows file sharing is working)
Now we've bought a new computer which is a mac pro with fresh install of leopard, i setup the windows file sharing, but i was surprised that i cant see my windows xp box too on the network, and vice versa, the pc cant see my mac pro too on the network, whats wrong with tiger and leopard file sharing???? please help me, im so frustrated cant make it to work. i know, my pc computer has nothing to do with it, coz i can still connect to a mac with panther os. hope someone can help me fix this... please..

This site has some information on file sharing and printer sharing between Windows and Macs for various combinations of OSs. The Leopard repository isn't quite as mature as the Tiger repository, but there's a lot of good information at this site. Hopefully, it will be helpful to you in resolving your Windows/Mac issues.

Bug? Folders created by transmission is read-only to Windows file sharing

It's a nice thing that transmission is supported in the LenovoEMC version of firmware. The thing is, folders created by this transmission are read-only, which means file can't be added, deleted nor modified from Windows file sharing (They are still be deleted with transmission though, but that's irrelavant).
From my experience, this issue is caused by the value of unmask not properly set up in the settings.json file. This file can be modified when transmission is not running, but I didn't find a way to stop transmission from running / restart itself even after being killed from SSH.
Please help.

You have to have root access (which will void your warranty) to modify settings.json, that's why I wish Lenovo can come up with an official solution.
If you don't mind viod the warranty, then after you stop transmission, you can log in as root via putty, then use nano to modify settings.json as mentioned below:
http://forum.nas-central.org/viewtopic.php?f=279&t=7877&sid=30b572be20744201c78d224e3db49c97&start=1...

Help with s-l-o-w-w-w-w-w Windows file sharing

After much hair-pulling, I finally got windows file sharing working on our 10.4.4 xserve (opening up ports 137-139 helped a lot!) - however I have noticed that directory navigation from the PC's are extremely slow... it takes about 25-30 seconds to navigate from one dir to another... once you navigate into a dir, and then back out, it seems that the next attempt into that same dir is very fast.
Any tips are appreciated.
Windows PC's are running XP Pro SP2.

There are several threads about improving Windows performance over smb. Do a search for "smb slow" to find them.
The single biggest thing you can do if you're dealing with a lot of little files is to do: sudo sysctl -w net.inet.tcp.delayed_ack=0
To add this permanently to your server add 'net.inet.tcp.delayed_ack=0' to /etc/sysctl.conf
There a bunch of other edits discussed here:
http://www.macosxhints.com/article.php?story=20040201121437157
=Tod

Windows File Sharing behaving differently on 10.4.5 ( iMac vs. Mini Intel)

I have and iMac and a Mini Mac Intel Duo configured the same:
jdoe/password/workgroup ( bot Macs have a user name jdoe)
personal file sharing started
windows file sharing started with jdoe account enabled
From the PC I ping both Macs to check network connectivity.
From the PC command line I use the following command:
net use i: \\imac\jdoe\Public password /USER:workgroup\jdoe /persistent:no ( works fine )
net use m: \\minimac\jdoe\Public password /USER:workgroup\jdoe /persistent:no ( logon fails )
The SMB connection to the iMac always succeed but the Mini Mac fails. Checking the Ethernet trace, I see that as expected Windows sends out SMB/CIFS packets on port 445 but the iMac does not replay so Windows try SMB/CIFS packets on port 139 (netbios) and gets a reply.
However when attempting to connect to the MiniMac, the MiniMac responds to the first packet on port 445;Hence, WinXP does not attempt port 139.. the negotiation is performed over port 445, but fails authentication.
A few things bug me about this: Why does one Mac respond to port 445 and the other on 139? Why does the failed negotiation on port 445 seems to progress until the NTLM challenge authentication failure? Is there a password issue between the two Macs? Both are running 10.4.5 out of the box, with no extra software!
Mini Mac Intel Duo & iMac G5 Mac OS X (10.4.5)

More notes... If I enable firewall on the MiniMac and allow Windows File Sharing, the Mini Mac only responds on port 139 Not port 445. Good, this is the same as the iMac default behavior, however, the login still fails.

Reseting the Hashed Password after enabling Windows File Sharing

Disclaimer: you'll need a good bit of knowledge about OS X, UNIX, and encryption to understand what I'm talking about.
All right, so normally OS X hashes user passwords using a salted SHA1 encryption. It uses shadowing so that you can't obtain the actual hash value using "% nidump passwd".
BUT, if you enable Windows File Sharing, all that changes. OS X re-hashes your password using the much less secure LANMAN encryption. This allows Windows machines to access your files. (LANMAN is what Windows used to encrypt passwords up through Windows ME. Later versions of Windows use NTLM instead, which is stronger.) This is why, the first time you enable Windows File Sharing, OS X warns you that enabling the feature will require your password to be stored in a less secure manner; it's downgrading the hash from SHA1 to LANMAN.
My question is: I'm done sharing files with idiot Windows users - how do I force OS X to go back to storing my password using SHA1?
Thanks guys.
-Bryan

Thanks biovizier. You're absolutely right, deleting the extra text after ";shadowHash;" and then reseting the password for the user's account does seem to force OS X to rehash the password using SHA1.
Just in case someone else has this question in the future, here's how to verify that your password is hashed in SHA1:
Log in as Root and open the /private/var/db/shadow/hash folder. You'll see files with long, weird names. You'll also see an XML file (with the extension *.state) for each of the files with long, weird names. The XML file contains several tags that tell OS X information about the hashed password - things like when it last logged on, when it was created, how many times login failed, etc.
We're interested in the other files - the ones that don't end in ".state"
To verify that SHA1 is being used, open the long, weird files in textedit. You should see something like this:
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000059G31HJ75BR54210P07Y57BC57094D643H78K8765L98C6X000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000
There should be a few more zeros; I've cut some out here to save space.
What should NOT exist, is the following:
57Y083D243109VGR45Z4B65812R8M087H65HJ8OK95T89L8JHL9000000000
000000000000000000000000000000000000000000000000000000000000
0000000059G31HJ75BR54210P07Y57BC57094D643H78K8765L98C6X00000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000
The second Hashed value does not start with zeros. This hash value is not SHA1. It is the less secure encryption method required for compatability with Windows.
If your hash file opens with zeros, you're using SHA1. Otherwise, follow Biovizier's procedure: Open NetInfo, select the user account whose password needs to be changed back to SHA1, look at the "authentication_authority" value, make sure the value is set to ;ShadowHash; and that no additional text follows that string, then reset the affected account's password. You can then log back in as root and re-check the hash files using textedit and you should find that the hash file opens with solid zeros instead of letters and numbers.
Do NOT manually edit the hash files in textedit. One of those files is the hash for the Root password. If you change that hash file, your root password will no longer work (because when you type MYPASSWORD, OS X will hash that string and find that the hashed value no longer matches the stored hash value in /private/var/db/shadow/hash and OS X will therefore reject your password as incorrect) and you will quickly find yourself locked out of your computer for good.
And finally, just in case you have the computing power of the NSA and are thinking about running the hashes I've listed here: A) They aren't the right length; I've left some characters out and B) I randomly substituted different alphanumerics in for the ones in my real hashes with no rhyme or reason.
Which brings me to another point: NEVER post your hashes online. Yes, it takes a TON of computing power to break them, but still, they're hidden away for a reason!
Anyway, I hope this helps other security buffs out there.
I'm going to make a suggestion to Apple that OS 10.5 be changed so that when you unclick "windows file sharing" the OS immediately rehashes your password in SHA1 again.
-Bryan

App that can access windows file sharing

Hello... I've got my Nokia 500 today, but i'm looking for an app that can access windows file sharing via wifi. I want to transfer my picture from cellphone to my computer via wifi..
Nokia 500 -> Wifi -> Computer (Windows File Sharing)...
Anyone please create an app for me

Telexy SymSMB used to be such an app, but was taken off the market (Nokia demanded it, because apparently some Nokia employees were involved in developing the app). Don't know if anything similar has come out since then.

Apple has broken Windows file sharing in Snow Leopard

Hi Folks,
Having a serious problem here.
Apple has broken Windows file sharing in Snow Leopard. Many others on the forums are experiencing the same thing. I was almost ready to fully switch to the Mac, then I thought I would upgrade to SL, then this happened...
OK so I have a Windows Server 2003 Small Business Server. It's pretty much the same as the standard Windows 2k3 server except that it throws in a few extras (And takes some things away). I'm also lead to believe, that there is a difference w.r.t. password signing/encryption or something?
Anyways, if I try and connect to my SBS server with the correct username and password (In different formats: Domain\username or just username), I get a "Unable to connect to server. Check IP..." blablabla. This happens after the password prompt has come up.
If I try and connect to my standard windows 2003 server box, it does work, just very slowly (Again, referring to the whole thing about how SBS treats password security differently).
So I ask a couple of things:
1) It would be appreciated if any other forums members could maybe help me get this going?
2) A plea to Apple - please fix this. It all worked perfectly in Leopard!
Apple probably haven't tested SL against SBS 2003 server. A lot of companies don't do this either as they think that it is just the same as the standard 2003 server (Which i hope Apple have tested against!)
Thanks guys

I have the same problem. Here are the details:
External Hard Drive with LAN (Buffalo Drivestation Flexnet: http://tinyurl.com/kk5mmu)
Mac OS X 10.6, on 3 different Mac Mini's
This error occurs on all computers when trying to copy a file to the 'SHARE' sharepoint on the SMB Drive:
"The Finder can't complete the operation because some data in "filename" can't be read or written. (Error Code -36)"
I CAN
Access / Read / Write this Drive in Windows XP
Access / Read / Write this Drive in OS X 10.5.7
Make new folder on this Drive in OS X 10.6
See a .DS_Store file which 10.6 has written to the Drive
Save a document to the drive from the Text Edit save dialog in 10.6
Save a document to the drive from the Pages save dialog in 10.6
Duplicate a document on the drive using Terminal (cp Untitled.pages Untitled2.pages) in 10.6
Copy anything to any other computer on the Network using 10.6
I CAN NOT
Copy a document to the Drive in 10.6
Duplicate a document on the Drive in 10.6
Save a PDF or JPG to the drive from the Preview save dialog in 10.6
This error happens every time. It is easily reproducible.
I hope that this information helps Apple get on to the problem soon.

Why did I have to enable Windows File Sharing to share files between two Mavericks iMacs?

File Sharing failed between my Mavericks iMacs. The console logs showed that the target iMac saw the ntlmv2 protocol as unknown to the kdc. I fixed it by enabling Windows File Sharing on the target Mavericks iMac. I had tried disabling SMB on both iMacs and leaving AFP on, but then nothing happened when I tried to connect. Why did I have to enable Windows File Sharing to share files between two Mavericks iMacs?

When you enable file sharing you need to have either SMB (Windows) or AFP (historically Apple-native) file sharing checked. The default in Mavericks is SMB, and not AFP.
If you uncheck both, then the system will turn off file sharing. Apple supports the use of both SMB and AFP connections in Mavericks, so with only AFP enabled you should have been able to establish a connection, but there could be a small bug or configuration-specific snafu that you're encountering.
With AFP enabled only, try pressing Command-K in the Finder to open the Connect To Server dialogue, and in here enter the address to the system using afp:// as the protocol, such as the following (the name can be looked up in the Sharing system preferences):
afp://my_imac.local

Command to Start/Stop "Windows File Sharing" on OsX Tiger Client

Dear Mac Gurus:
How to use command to start/stop “Windows File Sharing” on OSX Tiger client?
Thanks!
Max

Hi Max,
Windows file sharing requires two daemons, nmbd and smbd. They can be started/stopped as follows:
To start (type the following all in a single line):
sudo launchctl load -w /System/Library/LaunchDaemons/nmbd.plist /System/Library/LaunchDaemons/smbd.plist
To stop:
sudo launchctl unload -w /System/Library/LaunchDaemons/nmbd.plist /System/Library/LaunchDaemons/smbd.plist
The option "-w" indicates that the default setting (whether start them at boot time or not) is also modified (the same effect as you turn them on/off via System Preferences -> Sharing). This means, if you start them and shutdown your Mac without stopping them, then they will be automatically restarted next time you reboot the Mac.
If you use "load -F" instead of "laod -w", then they are started but the default setting is not modified (if it is off then remains off).
If you use "unload" instead of "unload -w", then they are stopped the default setting is not modified (if it is on then remains on and will be started at next reboot).
If you feel the commands are too long to type, then you can devide them into two commands, for example:
sudo launchctl load -w /System/Library/LaunchDaemons/nmbd.plist
sudo launchctl load -w /System/Library/LaunchDaemons/smbd.plist
See launchctl man page for more detail.
HTH
PowerMacG4, PowerBookG4, iMac(C2D) Mac OS X (10.4.9)

Windows File Sharing - Slow only in one direction?

Hi everybody,
I'm having a really strange problem with my network. I'm copying files between my G4 Mac mini and Windows XP Home machine, both with all of the latest OS updates. The computers are connected via a 10/100 switch and both are connecting at 100baseTX, full duplex. I have Windows File Sharing running on the Mac mini and I am sharing my entire user directory on the Windows machine as well. So I'm doing all of the file sharing over SMB.
Almost everything works fine--there's just one issue: file copies from the Windows XP machine to the Mac are incredibly slow. Transfers in every other direction work fine. If I connect from the Mac to the Windows machine and copy a file to the Windows machine, or if I'm on the Mac and I download a file from the Windows machine, it's fast. It's also fast if I connect from the Windows machine to the Mac and copy a file from the Mac--a 16 MB file copies in 5 seconds or less. But if I'm on the Windows machine and I try to copy a file to the Mac, it goes VERY slowly--a 16 MB file copy is now measured in minutes instead of seconds.
I googled around and found some people adding a line to their smb.conf file to fix it, but I tried adding the line to no avail (and of course, restarted windows file sharing and killed smbd to make sure it re-read the config file). I also saw some people who fixed it by making sure the network cards on both machines were manually set to 100baseTX, full-duplex--tried that too, didn't make a difference (it's autodetecting properly in my case anyway).
Anyone seen this before? I'd appreciate any suggestions. Thanks! By the way, I just completely reformatted the Windows machine and did a complete reinstall of Windows XP(why do you think I prefer Macs? ) and it had this problem before as well, so as far as I know, the Windows machine doesn't have some crazy virus or something causing it.
Doug
Mac mini G4 1.42 GHz Mac OS X (10.4.6)

Thanks for the reply! I had been on that site but I had been getting there through Google, so I went ahead and did a search on the site and found an article about speeding up Samba:
http://www.macosxhints.com/article.php?story=20051107090652912
There was a discussion below the article with people who had problems similar to mine, so I tried a suggestion near the bottom, adding the line:
large readwrite = no
To the Mac's smb.conf file, and now everything is fast like it should be. Thanks for pointing me in the right direction! This problem has been plaguing me for months.
Mac mini G4 1.42 GHz Mac OS X (10.4.6)

No windows file sharing on mobile acount ?

why can't i do file windows file sharing on mobile acount ?
PowerBook G4 Mac OS X (10.4.5)

sorry for not being clear.
i mean a mobile open directory acount from a tiger (10.4.5) xserve.
we have Canon ImageRunner C3170 at the office and it needs conect my user's computer via smb to deliver documents that they just scaned.
i can have the copier send the files to theire home directory on the server, but my user will have to wait 5 minutes to see it on thiere desktop (i sync theire home folder every 5 minutes) or do a "sync now".
it would be best to just have it send to thier computer direcly.
thanx

Windows File Sharing Folder Name Error

Hi, I’m new to the forums but I really need help and I was hoping someone could help?
I’m using a Mac os x server. We are having problems with the Windows file sharing. When we share drives they share fine. But on windows machines some of the folders in these drives have problems. Some of the folders names in the share have different names.
For example in one folder we had a folder called “PROPOSALS” this is fine on the Mac workstations but on windows machines the folder name will show completely different on windows. The folder proposals showed as “PDJ45~6H”. This has happened all over the share to loads of folders at random. Thats not all though if we tried to open these folders we get an error saying that it’s not accessible.
This has happened all over the server meaning loads of data is inaccessible by some of us on windows machines. What is causing the problem and what can I do to sort this out?
Thanks Tom

More notes... If I enable firewall on the MiniMac and allow Windows File Sharing, the Mini Mac only responds on port 139 Not port 445. Good, this is the same as the iMac default behavior, however, the login still fails.

CUPS printer sharing across subnets?

I am trying to set up my local network printer so that everyone in the house can print from it. However I have two subnets in the house and I don't see how to connect to the Linux server through a Windows 7 client.
My network is like so:
Upstairs: [Modem] <=eth0=> [Router 1] Subnet of 192.168.0.*
[Router 1] <=wlan0 client mode=> Downstairs: [Router 2 with dd-wrt firmware] Subnet of 192.168.1.*
[Router 2] <=eth0=> CUPS server/PC with USB printer attached IP address of 192.168.1.1XX
This works: [Router 2] <=ath0.1 virtual wireless ESSID=> Windows 7 Laptop
This doesn't: [Router 1] <=wlan0=> Windows 7 Laptop
I tried
sudo cupsctl --share-printers --remote-any && sudo systemctl restart cups
on the host PC, but the W7 clients can't connect across subnets. Is there anyway to set it up so it can? They can easily connect to the ath0.1 network and then print, but it's inconvenient for them. The Windows users spend most of the time upstairs, and not downstairs, so they are usually connected to the wlan0 network.
I have the option of putting [Router 2] into client bridged mode so it shares the same subnet of [Router 1], however I can't seem to set it up properly and I run into problems. It is important to have the ath0.1 network downstairs, and I am unsure that client (bridged) mode will allow for the virtual interface.
I do not have Samba installed but I am considering trying that, but a simpler solution would be appreciated.
*Edited for further clarification & error fixing.
Last edited by felixculpa (2012-12-27 20:03:51)

DiverDoc wrote:
if I can share a printer between an XP system and a Win 7 system?
Before I enter all the system data, I just wondered if someone already knew the answer to this one. I was successsfully sharing a non network printer plugged into an XP machine via USB and printing to it via Network Magic from my Vista machine, but since I upgraded Vista to Win 7, I cannot. Everytime I try to install the remote printer or access it in any way from my Win 7 machine, I get the Windows message: " Windows cannot connect to the printer". This also occurs form within the Network Magic Map if I try to Complete Printer Setup. It shows up on my Win 7 machine when I want to ADD a Printer, but I cannot install it. It shows as Shared on the XP machine.
Thanks for any assistance!
S.
Hi S.,
You need to use Network and Sharing Center and open up your computer. You need to use the Public Profile and turn on Network Discovery. Not sitting in front of Windows 7 at the moment.
Otherwise, you need a Wireless Printer or All-In One Machine or a Printer that plugs into the Router using an Ethernet Port.
thecreator - Running Network Magic version -5.5..9195.0-Pure0 on Windows XP Home Edition SP 3
Running Network Magic version -5.5.9195.0-Pure0 on Wireless Computer with McAfee Personal Firewall Build 11.5.131 Wireless Computer has D-Link DWA-552 connecting to D-Link DIR-655 A3 Router.

Windows file sharing across subnets

Similar Messages

Maybe you are looking for