network workgroup problem

G

gschoenthal

Bit poster
I just got a new MacBook Pro. After I got it, I installed Parallels (build 1970) on it. I set up both the Mac side and the Parallels side of the MacBook Pro with the workgroup name that we use at work which is "vdi". I'm not sure if bringing my MacBook Pro online did this, but since about that time all the computers at our work site give the attached pictured error when you double click on the VDI workgroup, yet if you know the path to a particular computer within the VDI workgroup you can put that in windows explorer on any machine and are able to access that computer.

After hours of pulling my hair out, I found a work around at the following web address ( http://www.annoyances.org/exec/forum/winxp/1139614862 ), but I'd like to know what really happening. This work around allows the computer that it is executed on to see any other computers that the workaround has been executed on, but not the computers that it hasn't been executed on. Also, this work around does not help out our Network drive, which the work around cannot be executed on.

I really don't see how my MBP (either through the Mac side or through parallels) could have done this to the rest of the Windows machines, but maybe I'm missing something. I tried contacting Parallels about it (even purchased a $30 phone support where I left a message, but they haven't called me back).

Any thoughts about this really annoying behavior?

Let me know if any other particulars would be helpful.

Thanks,

Gerhard
pastedGraphic.jpg
 
is it a Workgroup or a windows Domain you have at work. That message usually occurs when you arent a member of the domain and try to browse the computers in it.

One way to try, if it is a Domain you have at work, make sure the username and password you log into the VM with, is the same as your username and password you use in the domain.
 
Last edited:
Hi,

The problem miraculously fixed itself overnight, but it is a workgroup in question, not a domain. I will update this thread again if the problem comes back.

Thanks,

Gerhard
 
You must log in or register to reply here.
Back
Top