Puppy Linux Discussion Forum

[daveb]

I have a Windows ME box for legacy software that was running on a Windows network with another Win ME machine. The other Win ME machine left and was replaced by a computer running Puppy 4.3. When I use Pnethood 0.65 it shows no shares, even though there is an entire disk that is shared on the Windows machine. Pnethood does find the computer on the LAN, just no shares. Anyone have any suggestions on how to get them to work together?

Dave,

[fernan]

One suggestion is to check if you are scanning the windows network as a user with the appropiate permissions.

I've never used Pnethood , but usually there is an option like "scan as user" or something like that, that allow you to type a user and password that have access to the windows folder.

Also check in te preferences that you are in the righ WORKGROUP. It must be a place where to set that.

[daveb]

The way Pnethood works is that when clicked, it automatically runs a scan and finds the Windows ME computer and displays its name, which is very cool. It also says no shares found, and gives a place to put in the user name and password. The Windows machine is not password protected at this time. So no matter what I enter, it finds no shares.

I know that the Windows settings are ok because a number of larger (and slower ) Linux distributions find the files and allow R/W. So my guess is that there is a bug in Pnethood.

Dave

[Sit Heel Speak]

This may or may not directly help, but I saw the same problem just yesterday. A Win98SE computer which Puppy had previously seen the shares on, now the computer could be seen by PNetHood but the shares could not be seen.

The only difference from before, was that I had tried (on the Puppy machine) adding OpenDNS and other open-source-community DNS IP's to /etc/resolv.conf, per the instructions in this thread.

Reverting /etc/resolv.conf to the single line

nameserver 192.168.2.75

where 192.168.2.75 is my DLink DI-604 router (through it, the two machines are connected), which has DNS functionality...restored the ability of PNetHood to see the Win98SE machine's shares.

Any combination in /etc/resolv.conf of the OpenDNS etc. servers, with or without the DLink's IP, no matter whether the DLink's IP was listed first, last, or in-between, resulted in PNetHood not being able to see the Win98SE machine's shares, even though PNetHood could see the Win98SE machine.

The only way to see the Win98SE machine's shares, was to put just the single line in /etc/resolv.conf.

[daveb]

Sit Heel Speak,

You sir are a genius! Thanks for the tip -- it works great.

Dave,