• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Linux VM SMP2 monitoring from Windows 7 x64 HFM

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Audioaficionado

Sparkomatic Moderator
Joined
Apr 29, 2002
OK I'm so close I can almost touch it :bang head

HFM browser.jpg

network.jpg

log in failure.jpg

I'm using the same user and pass for both ends.

I shared the FAH folder in my VM

What little thing did I leave unfinished?
 
I'm not sure how you have it setup, but I can probably help. For any step that you get stuck on, be sure to check the samba logs, usually found at /var/log/samba/xxxxxx (where x is the computer/IP you are accessing from). You can use "tail" to get the last few messages. This can give you hints as to what is going wrong ("Password incorrect", "Access denied", etc).

On the server, did you create the user audioaficionado and set the samba password ("smbpasswd audioaficionado")? Did you make sure that you are added into the share that you created? If you modified the samba configuration, did you restart the service?

Windows also seems to be adding the computer name "Trinity" to your authentication, which can cause issues. Click on "Use another account" and type only the user you are trying to connect as.
 
if you allow guest access (check all three boxes in sharing in Linux), you shouldn't have to mess with samba passwords or do anything to samba except install it. Probably the issue is on the windows 7 side, though if the two machines aren't in the same workgroup, you will have issues. Samba defaults to Workgroup = workgroup.

IN Windows 7 advanced sharing settings you shoud be set as follows:
turn on network discovery
turn on file and printer sharing
turn on sharing so anyone with network access
media streaming doesn't matter
use 128 bit encryption
turn off password protected sharing
use user accounts and passwords to connect

That's what worked for me.
 
I do the guest access deal and leave the workgroup alone... still works for me connecting from Win7.
 
It probably will unless you do something like make the Win 7 rig a member of the MSHOME Workgroup and leave the VM in Workgroup, it might work even then. I've always kept them in the same workgroup.
 
Well I finally got access to my windows shares from within the Mint/Debian Linux VM, but no love the other way I really needed it.

Anyway I ended up killing the internet access in the VM and just switched to my trusty old Lenny VM with vmtools already installed. None of that Ctrl+Alt nonsense. However I still need to install Samba in Lenny so I can share. Meanwhile my PPD is ramping back up to 10k+ for the single machine. My adult kids keep shutting down the GPU clients on their machines because they game and then forget to restart it when they are done. I might as well uninstall them for all the good they are doing me or Stanford :rolleyes:
 
If your kids are gaming on XP rigs, you can install the Microsoft toolkit to get the sleep command. Install the GPU client as a service. Create a script with a shortcut on the desktop that stops the service, sleeps 4 hours and then restarts the service. It's been a while since I did that, but it worked for me.
 
It probably will unless you do something like make the Win 7 rig a member of the MSHOME Workgroup and leave the VM in Workgroup, it might work even then. I've always kept them in the same workgroup.

Humm, all my windows rigs are a member of another workgroup. Not MSHOME, not WORKGROUP, but something else I chose. Again, leaving the samba setup automatic still works for me.

The only thing that's a little annoying about setting it up this way is that I get no NetBIOS name resolution from the linux box. I have to access it directly via the IP. Did you try that Audio?
 
I had the same issue at first. seemed the ip route worked, then a few days back the netbios names popped up, and I had to edit my clients in HFM with the new netbios name. I dont know if i missed a step or maybe did not do a restart after the install of SMB... but either way, the IP route worked until netbios was refreshed.
 
Perhaps if in the same workgroup, you don't have to use the IP address? I know I've never had to.
 
Back