Find solution
How do I change the computer's ID on my Mac?

Windows won't serve to Mac

  • Problem: OSX to Windows direct-wired ethernet connection works, but the Mac can't see the shared PC drives. The PC and the Mac are both normally on wifi but the Mac's Airport is turned off now. Both machines have manual addresses set on their ethernet NICs, with direct CAT5 cable between the two; PC = 10.0.0.1/255.255.255.0; Mac=10.0.0.2/255.255.255.0. (The cable isn't a crossover, because OSX now manages that.)Ping works in both directions (i.e. from either machine to the other.) I want to connect from the Mac to the PC's share D, so I do flower-K to connect to smb://10.0.0.1/D. First time I tried the Mac's dialog showed "Connecting" then radio buttons for 'guest' or "name + password". Because the PC's guest account was off I tried the PC's name+pw but OSX rejected it (and other names+pws) and said "not allowed..." [NOT the exact words, and I can no longer get this dialog]. I enabled the PC's guest a/c and tried the guest radiobutton on the Mac's Connect to Server. No success. Now the Mac doesn't ask for name and pw at all, and there's no guest/ID+PW choice nor radiobutton. Every time I try to connect from Mac to smb://10.0.0.1/D (or other share on the PC) the response after trying to connect is "Connection Failed. You do not have permission to access this server." Windows Local Security Settings policies are not assigned. Do I need to change any other security settings? As mentioned Airport is disabled on the Mac, but it's active on the PC. Another Mac here can share the PC just fine over wireless; no problem logging in - pretty much any username+pw works, it's not picky. I need a fast connection though, to get stuff onto the new goodness of Mac (fresh yesterday. Yum.) Hw/software: Macbook 13"; 2.1 GHz core duo; 1GB; internal NIC; running MacOS X .5.2. Windows XP Pro sp2 on homebuilt PC (ASUS mobo, Athlon 1500+ @ 1.3 GHz) 512 MB; Intel PRO/100 NIC. (Both OSes have current updates.)

  • Answer:

    Huh? Last time I checked, there is no way to just "hook up" two ends of a cat-5 cable to two computers and expect it to work without reversing the Tx signals, particularly not when the two systems in question are a Mac and a PC. No way, Jose'. All macs with 1000BaseT ports have http://www.transition.com/pshelp/cross.html. Have for years (actually, I thought most modern Dells were this way too). So this shouldn't be a problem. Windows file sharing is a complicated beast. Here are a few things that could be wrong (I would try them in order): 1) Does the user have a password? By default, accounts with empty passwords are not allowed to connect over the network. 2) Are you trying to connect to the D: drive? In that case, the share is really D$. 3) If you're trying to use the default drive shares (C$, D$, etc) then you need to connect with an account that is in the Administrator group. 4) Is Windows Firewall turned on? Try turning it off for the moment. 5) Is the McAfee or Norton firewall on? Try turning these off for the moment. 6) Go to Start, Programs, Administrative Tools, Local Security Properties (you'll have to enable this by right clicking on Start, click Properties, Start Menu, select Classic Start Menu, click Customize..., and under Advanced Start menu options click "Display Administrative Tools"). Select Local Policies, User Rights Assignment: a) "Access this computer from the network" should have a group in it that includes your user. b) "Deny access to this computer from the network" must NOT have a group in it that includes your user. 7) Right click on My Computer, Manage, Services and Applications. Are the following services started: Computer Browser, Server, Workstation? 8) Share permissions are complicated beasts in Windows. Turn simple sharing off (it's somewhere in the folder preferences). There's two levels of permissions. First, there's the file permissions that you see by right clicking on a folder, then click "Properties", then "Security". These are the base permissions. Then there's also the share permissions, by clicking the "Sharing" tab, then "Permissions". These are overlayed on the base permissions, and can only make things more secure. For example, suppose the base permissions give the Users group read/write access, but the sharing permissions give read only. The network user will get read only. Now suppose the base permissions give read only, but the sharing read/write. The network user will still get read only.

airplain at Ask.Metafilter.Com Visit the source

Was this solution helpful to you?

Other answers

the mount command comes back with "mount_smbfs: mount error: /Users/me/Desktop/foobar: Broken pipe" The PC username has no password, so I'd entered mount -t smbfs //[email protected] .... given that the other mac can connect without pw i hoped this would be enough, but maybe the command is wrong that way?

airplain

All macs with 1000BaseT ports have auto crossing MDI/MDIX. Have for years (actually, I thought most modern Dells were this way too). So this shouldn't be a problem. No way! Now I feel old. :)

Civil_Disobedient

I need a fast connection though, to get stuff onto the new goodness of Mac (fresh yesterday. Yum.) Just for the record, I usually skip all of the Samba/disk mounting stuff and use WinSCP to ftp things back and forth to my Mac.

tkolar

I think I first installed Samba on Slackware in 1998, and got it working with an NT Domain (this was before AD; or at least before AD became popular). You'd think that after 10 years of working with smb I'd know what I was doing. But what I've got instead are 10 years worth of tips and tricks that amount to nothing more than superstition. Sometimes adding the domain/name before the user works. Sometimes not. I've got a Parallels XP VM that refuses to connect to a DFS share, but a crappy Dell across the room has no problems. But that Dell can't connect to any of the other workstations. As soon as you move a workstation outside an AD, abandon all hope of it working consistently. Anyway, glad it finally worked for you!

sbutler

YES! with a new user and password on the PC, mount has succeeded! THANKS SO MUCH SBUTLER! after mount -t smbfs //name:[email protected]/E ~/Desktop/foobar Finder can browse the PC through the foobar folder

airplain

You can also try using "Rio\user" instead of just "user". I'm out of ideas. Googling around looks like other people who moved to Leopard are having the same problem with mount_smbfs... but not a lot of helpful suggestions.

sbutler

sbutler all your help is very much appreciated! mount -t smbfs //Rio\;[email protected]/D ~/Desktop/foobar also gets "Broken pipe". i guess there must be some setting on the PC i need to fix. I'll create a new user on the pc with a password & try mount with that

airplain

Opps... make that: mount -t smbfs //FOOBAR\;[email protected]/D ~/Desktop/foobar Forgot you need to escape the semicolon.

sbutler

How about this: mount -t smbfs //FOOBAR;[email protected]/D ~/Desktop/foobar Where FOOBAR is the name of the Windows machine (not the workgroup name, the computer name).

sbutler

Load more

Related Q & A:

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.