Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

MacbookPro can't see Windows 7 Workgroup Computer Over Wireless Network

Posted on 2010-09-04
3
Medium Priority
?
986 Views
Last Modified: 2012-05-10
Can't seem to find an answer to my problem elsewhere, so I must ask.  I am new to Mac and there may be a simple solution that I am not aware of, but here goes.

Just bought a new MacBook Pro.  Trying o use my old laptop (PC with Windows 7 Professional) as a file server for external USB hard drive using a home workgroup.  Both computers use wireless network using a Netgear WirelessN access point and both using using the default workgroup name WORKGROUP.

The Mac has Windows 7 Ultimate installed on a bootcamp drive (Had to be done for work reasons - sorry).  When I am in Mac OSX, the PC shares do not show up.  If I try to find the PC manually by entering the IP in the Connect to server option, I get an error that the connection failed because either the server does not exist or is unavailable.

If I boot the Mac to the bootcamp (Windows) drive, I can see the network shares fine and can read and write correctly to them.

Any ideas how to make the Mac OSX work?
0
Comment
Question by:gboo19
  • 2
3 Comments
 
LVL 53

Expert Comment

by:strung
ID: 33604312
See if this tutorial helps:  http://www.ifelix.co.uk/tech/3024.html

0
 
LVL 53

Accepted Solution

by:
strung earned 2000 total points
ID: 33604316
Also, instead of typing in just the IP address of the Windows computer, type in:  smb://IPAddress

or smb://IPAddress/sharename
0
 

Author Comment

by:gboo19
ID: 33604502
Thanks Strung.  Went through step by step on the tutorial link.  Other than various differences between Vista and Windows 7 and between the tutorial version of Mac OS and my version of Snow Leopard, all settin gs match.  I get to the connect to server and get the same error.  I did find the problem here.  My Mac wants to start with smb://\\ and have me type the IP after the \\.  When I remove the "\\" and just do smb://xx.xx.xx.xx, it works fine.  Not sure why it wanted to add the extra "\\" after the smb://, but all works now.  Thanks for your quick response!
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

SUMMARY Enterprise backup in a heterogeneous network is a subject full of complications and restrictions. Issues such as filename & path structure, attributes and extended metadata always tend to complicate the subject to the extent where either …
In this article we will discuss some EI Capitan Mail app issues and provide some manual process to resolve them.
Screencast - Getting to Know the Pipeline
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…
Suggested Courses

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question