In Wary, "mount-FULL -t cifs" does not recognize the "-o guest" option. However, "mount.cifs" does.

Thanks, rcrsn51 for the information.
But I guess "username=guest,guest" is more safe.

Quote:

Are you aware that the Rescan and Refresh buttons no longer work like they used to?

Right. It doesn't work as for 0.6.6.

Hi,

I´m sorry for the lake of Updates and this late response. Many Enterprises systems chooses this season to Upgrade their core Applications...

Ok, about pnethood. What´s the problem with the Refresh and Rescan buttons?. I don´t have a single problem with that.

I didn´t made any test about the "username=guest,guest" change, but I believe this is fail save. You are trying to establish a new connection as guest (no password prompts) enforcing the connection with the guest user, I don´t have Windows Vista or 7 (no even in a sandbox machine) so will make some basic test in Win XP.

I hope to have some free time this weekend and release a new pnethood version, I'm writing an optional menu to add more command line options, so any suggestion is welcome.

shinobar, rcrsn51 many thanks for the feedback and the extensive test, I apologies for my partial/enforced retirement.

Greetings,
clarf

EDIT: I tested "username=guest,guest" with Windows XP. The results with a guest account:

Empty password: WORK
"guest" password: DOES NOT WORK

The "username=guest,guest" does work for Windows 7 as Shinobar claims. But it does not work for a guest account with a default "guest" password in my XP system, to achieve the same results that I get using "username=guest,password=guest" (it works for both cases, empty or default password), I should add a failover code to use the guest password when the mount command fails.

It´s a nice find shino, I´ll implement this for the next version. Last edited by clarf on Wed 19 Jan 2011, 22:51; edited 1 time in total

In XP-Pro, if you turn on non-simple file sharing, then "username=guest, password=guest" will also fail. That's because Windows tries to login to the guest account using the incorrect password "guest" and fails.

However, "username=guest,guest" will work because that disables the request for a password.

Quote:

But I guess "username=guest,guest" is more safe.

The safest way is to use YASSM so you have complete control over authentication

I wonder why it didn´t work for you.

In all my tests the "username=guest, password=guest" code works using non-simple sharing. I can open shares even when the guest password is empty.

Was having an ok time with 4.x, decided to go for broke and try Lucid and now I'm in a world of hurt.

Ok, on initial scan, I completely break a few servers on the LAN. I have no idea why, but if i dare to fire it up on the VPN, at least 3 servers that have windows shares decide to kick the bucket. Even a proxy server decides to puke and I set off some alarms. My bad, no idea how this even happened with whatever was provided with 5.2

If i do pnethood "ip.of.server.wanted" I get additonally a ReallyLongStringOfInformation on an additional workstation that for some reason I have no idea why it's even reporting.

That's ok, I'm sure that's a bug, which is ok.

But I finally got my target server, but I can't scroll the list of shares.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum