Went to 10.3.5 and can no longer connect PC
 

I've done some searching and I can't find the answer (just notes that others are feeling the same pain).

I upgraded to 10.3.5 and now I can no longer see my XP machine or connect to a shared resource on it.

Can someone advise or point me in the correct direction for self help.

Thanks!
Jason

This might be fixed by downloading and installing the 10.3.5 Combined Installer. This is still a good step that can fix a variety of issues that show up after doing a 'step' upgrade, such as 10.3.4 to 10.3.5
Also, what else have you tried? (repair permissions, reset caches, etc.)

I did the full 10.3.5 combined install
Repaired permissions from both in OS X and booted from install disk
Verified the XP machine was still sharing drives

If I browse to Network, then 'Workgroup' I am not seeing any of the other devices on my network (previously I would see the other 4 PC's on the network in the workgroup).

If I try to connect by IP, it times out the connection

If I try by the XP machines name, It doesn't find it.

Thanks for the help!

I have done the same and I also could not connect to my dad's XP laptop anymore. Minutes before I installed 10.3.5, I was on 10.3.4 and everything worked like a dream. I too would love to know how to solve this.

Well I don't know if I am going to be much help, as my problem fixed itself auto-magically. I verified I could ping, I could connect from the PC to the Mac, I checked to make sure other XP boxes could get to the PC in question. Finally I rebooted the Powerbook running OSX (again) and it worked.

So we'll see if the problem arises again or not.

Good luck!
Jason

Jason, thanks for your reply. Good that it works again for you. But I have tried exactly what you did several times and so far no luck. I just try again once in a while. We'll see when Apple solves this hickup.

What protocol are you using to connect to your XP machine ? Also, did you install the winxp sp2 yet ?

I always used smb (Samba) and no, I have not installed XP SP2 yet, as 10.3.5 broke the connection before SP2 came out. It is clearly a 10.3.5 problem. and has nothing to do with XP (this time :D).

I'm having the same problem, browsing a Win XP SP2 machine, it just times out. I don't know if it is coincidence but I only noticed the problem AFTER SP2 was applied to the XP machine. I've tried the steps above to no avail, anyone else any other suggestions? (I've always had to use the 'Connect to server' option though, I've NEVER been able to browse a PC through the Network Browser on the Mac (which has been upgraded 10.2 onwards). I can ping the machine and can Telnet into it though, so I don't know if that gives anyone any more suggestions?

XP sp2 turns on the XP firewall by default, whereas before it was off by default. In your case, I suspect you need to set up your XP firewall to allow smb.

Trevor

No, we have the XP firewall turned off. The firewall in use is Kerio which is set up to allow a trusted range of IP's 192.168.XXX.XXX so it shouldn't be that which is the cause of the problem either. (We have tried turning Kerio off but still no joy)

Just tried connecting a friends powerbook running 10.3.4 to the network and there is no problem connecting to the Windows machine, so the upgrade to 10.3.5 has definately broken something..... now the question is, how to fix it!!!

Not sure 10.3.5 actually breaks something, cause I have had no issues with smb or other remote connections. It actually is faster when connecting to Win machines... So the problem is probably specific to the setup you have, something you added, changed that I did not...
One question though... When trying to connect to your XP machine... do you simply put in smb://the.machines.ip.address and then clikc to login ? Or include the user name and/or passwor dlike you would do for SSH ?

Could be I guess, odd that other folks are seeing the same sort of errors though. I have tried the IP address (smb://192.168.0.2) which usually prompts for the share I want to mount, I have tried the IP address with the share name added (smb://192.168.0.2/winxp) which usually works, and I have tried an admin share (smb://192.168.0.2/C$) which also usually works. Today, for the first time I have tried smb://workgroup;username@netbiosname/share as detailed in the SMB guide and still no joy. I've tried deleting my finder prefs file (not sure if that is anything to do with SMB shares), I've tried repairing permissions, I've checked the services I have running, just about everything my knowledge extends to. All I know at the moment is that it worked on 10.3.4 and on 10.3.5 it doesn't. If I can't find a fix for this, is it really worth rolling back to 10.3.4? If so, I guess that would mean the total pain of a full reinstall?

This is a bit off-topic, since I can't throw any light on what is happening in 10.3.5, but thought I'd share some of the Windows weirdness that you can encounter.

In a related situation, I lost network ability from the PC when I updated to SP2. Troubleshot the hell out of it before realising that the network adapter card was defective. I had gotten it to work in SP1 by downgrading to Win2000 drivers, but that didn't work in SP2. Finally swapped the card and all was fine.

Thanks for your comments, but I think that the cards are not the problem here. I must be 10.3.5 which must have changed something. Let's hope Apple reads this and does something about it.

Well as I had a free Sunday afternoon, I thought I'd put this to the test on my own machine, just to make sure. I wiped everything clean, installed 10.3.4 Server and could connect to the Windows laptop no problems. After installing the 10.3.5 combined update, I was back to not being able to connect to the Windows machine. For me, it's more of an annoyance than a problem as most of my stuff is stored on the Mac, and of course, the Windows machine can still see all of my shares. Something that they need to fix though (Hope we don't have to wait till 10.4 comes out though!)

I remeber having similar problems a few times ago. I solved it by remving the entries related to the PC i wanted to connect to in KeyChainAccess.app. Apparently something went wrong with my password at the time of the upgrade, but not sure it will work.

This time, nothing would work, logging in as root, creating a new user, nothing. The Windows machine can be pinged OK (and still can) but after a complete erase and reinstall of Mac OS 10.3.5 the problem re-occours.

i had the same problem trying to connect to a network printer via ethernet - ended up reverting to 10.3.4 luckilly had a recent clone/backup so i did not have to reinstall everything.

10.3.5 seems to bone of those updates geared at pushing you to the next upgrade (probably tiger)

I can connect to my networked printer (HP Laserjet 2200DN) no problems, but yes I agree with you, break things in one update, so they can be 'fixed' for you in the next chargable update! Doesn't seem like the Apple way of doing things to me though!

I think before Tiger comes Apple will have fixed this in a 3.6 update. It is not Apple like to break something and then to charge for the fix.

Well I am back in this boat again. After the initial ability to connect, within the next 2 days I couldn't connect again and I am still not able.

I can even remote desktop by IP just fine, ping just fine, and connect from the PC to the Powerbook just fine...

Jason

Jason, what did you do to break it?? Do you remember?

Well after re-installing twice, and upgrading twice, it SEEMS that the upgrade to 10.3.5 resets the name of the workgroup back to default. I've changed this back now to what it should be, and hey presto, I can see the Windows machine again, so if you are still having difficulties, then, something worth checking out! I'll let you know of any updates!

Ah that would make sense. I remember that once I had updated machines to 10.3.5, I happened to set a new workgroup and change it on those machines... Had not tried to connect with SMB before doing so. Worth the shot, easy to check... but still would not explain why the update would do so while others never did...

I had no problems with SMB before 10.3.5 and afterwards I did, and the change of workgroup seems to be the cause of it. I don't know why the update resets the workgroup, but.... on this machine it caused a problem which is now fixed! (so far!! and thanks for all your help guys!)

So you changed the Workgroup name on the Mac? Could you tell us the procedure for doing this? I've always reverted to changing it on the PC end.

Thanks for the tip. But I have checked my workgroups on the PC and on my Mac. They are the same and on the Mac nothing has touched my smb.conf since December 2003. I still cannot connect from my Mac to the XP machine. Therefore, the hunt for the reason goes on (at least for me:().

Open your terminal and type You can also use vi or emacs or your preferred editor. Then find change the ????, save and restart the smb server.

GUI Alternative
 

Or you could use the Directory Access application in your utilities folder, just authenticate, highlight SMB cnd click configure. Type in your workgroup (On my setup the WINS Server box is empty). OK that box, make sure SMB is checked and click Apply. (That is on 10.3.5 Client, there is another way on OS X Server which I will explain if you need it

OMG! I can't believe, after all this time, I've missed this little jewel! Thanks! :)

Actually feels nice to have given something back to someone for once rather than just reaping information from others! :D

This fixed it for me!
 

I had the same problem, finally figured out what caused it.

I had recently upgraded to SP2 as well, and it reset sharing to "simple file sharing" by default.

Once I turned this off, 10.3.5 has no problem seeing the workgroup.

Simple File Sharing is the first thing I ever turn off on a Windows XP install. Basically, it makes Windows XP Professional act like Windows XP Home Edition (Which is not what I want!)

Same but diff problem
 

I am having problems seeing my mac 10.3.5 from my pc xp prof. I can share the pc files on my mac, but get an error message of not having access premission on the pc to access mac. It sees the mac but can't get into it. Where did you turn off "simple file sharing"?

thanks,

Joan