Windows Vista Home Premium Samba Problem -- could it be RPC?

Windows Vista Home Premium Samba Problem -- could it be RPC?

Post by aGFnczE5Nz » Mon, 10 Mar 2008 07:45:00

Hi there --

I conntected a new Vista laptop to the work's Samba file server with no
problems. Then, for no obvious reason it simply stopped working. I could
ping the server so I know that its there (apart from the fact that all the
other machines are XP and don't any problems), but I can't connect a drive to
it. Indeed, vista won't even see it if I type the IP address directly into
Windows Explorer.

I've tried everything I can find, including the HKEY hack that seems to have
worked for everyone I know:

No luck.

I've tried re-installing and that hasn't worked either.

The only difference that I can find between the XP machines and mine is that
I can't change the service name providor on the RPC options to Windows. If I
do, close, and then reopen it reverts back to blank, an option that doesn't
even exist on the XPs.

I've checked and the RPC service has started.

Any ideas?

Windows Vista Home Premium Samba Problem -- could it be RPC?

Post by ChrisBingh » Sat, 22 Mar 2008 17:10:52

On Mar 8, 5:45 pm, hags1975 < XXXX@XXXXX.COM >


From my understand there is a setting which you can set on your samba
server which will use the type of authentication that windows vista
uses. I also use Windows Vista I have the home premium version. If
you have tried this:

- Click start
- Type: regedit
- Press enter
- In the left, expand these folders:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\

- In the left, click on the folder named:


- In the right, double-click "LmCompatibilityLevel"
- Type the number 1 and press enter
- Restart your computer

and that did not work for you.... you could enable NTLMv2 support in
your smb.conf. By default NTLMv2 auth is not enabled. You would have
to add the following and restart smbd:

client ntlmv2 auth = yes

If that doesn't help I don't mind trying to give ya more ideas. Once
I get home from work I am going to be trying second method to see if
that repairs the issue.