Mac OSX Cannot See Windows XP Shared Folders

alene · #1 October 31st, 2009, 10:23 PM

Hello, I have tried to find a solution looking thru these forums but am not sure if any of them apply to my situation (due to other circumstances). I have a new IMac (OSX 10.5.8 Leopard) - I am a very new Mac user.

When I first I set up my Mac it immediately recognized the shared folders from my Windows XP machine. I did NOT have to configure networks or anything like that. I plugged in my Mac - the folders appeared in view. No problem.

But yesterday, in trying to repair issues on the Windows machine requiring that I disconnect net connection temporarily, Mac then showed a "lost connection" / disconnection to the shared folder. And from then on, it now cannot see the shared folders, nor can it even successfully ping the Windows pc.

Here's the current status:
Windows machine is hard wired - it CAN ping Mac right now.
Mac is (and always has been) on router. It can NOT ping windows.

These machines are about 2 feet away from each other on the same net connection.

Because I have never had to especially configure either machine to see the other- I was afraid to continue trying to negotiate new networks - when there may be some other problem and I am not informed enough about Macs to determine what it is.

I greatly appreciate ANY assist. What I am really trying to do is move a large amount of files over to use on the Mac - and I would rather have it direct on the network then start saving many gigs to a separate drive then manually installing them.

Thank you for your help. best,

djackmac · #2 October 31st, 2009, 10:45 PM

Have you tried restarting the Mac? BTW this would more appropriately belong in the Networking & Compatibility section.

alene · #3 October 31st, 2009, 11:26 PM

Yes, rebooted. Mac does not see any shared folders at all. It gives the following error: "Server does not exist - check name or ip"... Despite that the Windows machine can ping the Mac just fine.

[[Edited to add: Error specifically reads as "cannot complete operation because some data in smb://... could not be read or written. Error Code -36.]]

I have taken the following steps and getting the above error:

1) Go > Connect to Server >
2) Inputting: smb://ip/folder name -
3) also tried using actual machine name / folder name.

Still not working and Mac will not ping the Windows machine successfully either. I just don't know why and I read a good amount on setting up networks and all the info conflicted to one another. Also as mentioned, was never required to MANUALLY establish the connection and felt it would create more problems without trying to find out why it would suddenly not work just because the net connect was temporarily disabled....

Also: I have absolutely NO firewall or security on the Windows machine - so it isn't windows default firewall causing it. All windows share settings are right - sharing enabled in system correctly - so I don't know what to look for to resolve.

I am sorry - i did not see the specific forum - I noted there were some indicated NOT to post questions -- this one looked the most appropriate to post. Should I repost this or can this be moved there?

djackmac · #4 October 31st, 2009, 11:57 PM

I'd go into system preferences/sharing and make sure file sharing is enabled just to be sure. Then I'd have to know what happened to the Windows machines to make things different now. What kind of ips are on all the machines? Are they all still on the same subnet? Did you use applications/utilities/network utility on the Mac and try to ping the Windows machines?

alene · #5 November 1st, 2009, 02:10 AM

djackmac - first, thanks for your help. To your questions:

I'd go into system preferences/sharing and make sure file sharing is enabled just to be sure."- Done. In sys pref file sharing is checked and enabled. I have only this field checked so if there should be others - pls advise.

Then I'd have to know what happened to the Windows machines to make things different now.". I'll answer this at end.

"What kind of ips are on all the machines? Both machines have almost identical ip but for one digit. They appear correct to me.

Are they all still on the same subnet?" - Yes. Sub net exactly the same for both.

"Did you use applications/utilities/network utility on the Mac and try to ping the Windows machines?" Yes - none received; packet loss is 100%.

Now, the flip side - doing command prompt on the Windows machine - it pings the Mac just fine. And I made a point to ensure the subnet was an exact match (which it is). File sharing on both windows (and Mac as far as I can tell per the above) - is enabled.

What happened on the PC was process of scanning root for malware attack. This required disconnect of net connection (for about 10 seconds) and then restart. However, what I did not know was that concurrently, someone else was moving a graphic file from the shared folder on the pc to mac while this scan was occurring... At that point where the pc net connect needed to be reset - is when the "disconnect" pop up appeared on the Mac. I did not expect a major issue because the only impact was the interruption of the net connection on reboot. So it could be the sequence of events here but again - I don't know enough about Mac's to know exactly why - nor why it would not be able to see the PC henceforth because of a net connection interrupt. If you have any thoughts I appreciate it. Thanks.

djackmac · #6 November 1st, 2009, 02:54 AM

Quote:

Originally Posted by alene

Also: I have absolutely NO firewall or security on the Windows machine - so it isn't windows default firewall causing it. All windows share settings are right - sharing enabled in system correctly - so I don't know what to look for to resolve.

I think you are barking up the wrong tree in regards to suspecting the Mac is the culprit, which is understandable under the circumstances. I suspect its something on the Windows machine blocking the connection. I know you said no security is enabled but Nortons is notorious for blocking connections even when disabled. Many times it takes a complete uninstall to get Nortons hooks out of Windows connectivity. This is why just about every third party AV developers are releasing uninstallers for these types of issues along with others. Another thing you may want to check on the Windows machine is perhaps resetting Winsock, especially if malware was found. Sometimes removing the malware will hose the Windows Winsock registry settings. These are usually easily fixed through the command line (netsh winsock reset catalog) is what it is if memory serves me. Google will tell you for sure.

alene · #7 November 1st, 2009, 12:38 PM

I have never had norton's. The windows machine is free of any other reg, dll, files, exe etc. So that's definitely not it.

I will try resetting winsock but don't think that's the issue. I think the issue surrounding the Mac prompt of "disconnect" --- it appeared very quickly.

Which is why I don't think asking this question in a Mac forum is :barking: up the wrong tree. Don't thing winsock is the issue. But thanks for your help.

Satcomer · #8 November 1st, 2009, 12:40 PM

Are you runnings the Windows software firewall (or any others software firewall)?