4.1.2 can't browse Windows LAN neighborhood
 

Hello!
I'm essentially a newbie to Puppy: I used to have 1.0 loaded on this old Pentium-MMX 200Mhz client w/in my home Windows 2003 network. I recently upgraded to Puppy 4.1.2 but found no linNeighborhood (okay, where have I been?) and don't see Gfilemanager. I can't get Pnethood to see anything on my LAN, although I do have Puppy in my subnet w/ the stats I spec'd for my LAN layout. (Same settings as w/ v 1.0) I really like the look of 4.1.2, but feel on the virge of using another system if I can't see the network... also as I now have three other older PCs for potential Linux systems.
Please advise on getting a network browser working under Puppy 4.1.2 i.e.: Do I need to download/install a supplemental app if they've left out a neighborhood browser...? If so, what pkg do you recommend and what are the basic steps?

Notes:
1) I do have Internet connectivity w/ this 4.1.2. Puppy.
2) Separately, I do have an Ubuntu client which has no networking issues w/in my LAN. i.e.: All seems up to snuff otherwise.
3) I also tried pnethood "[Server],[puppypc]" and found smb and cifs mounting enabled, however, receive only messages like:
"/user/local/apps/pnethood/pnethood: line 445: 5459 Terminated gtkdialog3 --program=MSG_SCANNING_MACHINE --center 192.168.0.0/16"
4) I've searched for related threads..

Please advise. Thanks.
aNeumann

Al,
Try adding the 3.0 version of LinNeighborhood by downloading via Menu, Setup, Puppy Package Manager. i.e.: The Pkg Manager works kind of like Synaptic under Ubuntu.
Regards.
Al

Al,
Thanks -golly gee, it's a big jump from v. 1.0 to 4.1.2
Anyway, I downloaded and installed LinNeighborhood (LN) for v. 3.0 along the the dependent packages/libraries. Although LN functioned, it cannot create a folder-level share- or mount a folder -on my Windows 2003 Server. Apparently MS effectively shut down smb connectivity in a way so only cifs will work. On to another solution (?)
Downloading and attempting Gfilemanager, I found it can't even find nmblookup, yielding error "The command nmblookup was not found, refusing to scan." This is really strange, as nmblookup can be found and used via Console commands. On to yet another solution. (?)
Okay, I then returned to Pnethood. After a couple dozen go-arounds with Refreshing and Rescanning, along with some jockying of LN (although I'm not sure it had any influence), I finally got mounted to my Windows 2003 Server drives and could access its folders. But wow! -what a cumbersome layout under Pnethood! When are they simply going to get cifs working for LN or provide an even better GUI a la MS Network Neighborhood / Windows Explorer. (Hey, it doesn't have to really be "MS"-like, but Pnethood GUI took a step backward.)
Any other alternatives toward smooth, comprehensive Network neighborhood functionality?
Please advise.
Thanks.
Al

Al,
Glad to hear something works -sort of. Yes, Pnethood is also still 'buggy'. Just amazes me too that they don't just expand a little on LinNeighborhood and w/ cifs.
Al

Al,
What's really goofy is that all my other Linux distro's had no problem connecting w/ my Windows 2003 Server shares. I wasn't faced with smb signature limitations, as well as didn't have a buggy browser or
Sure wish that if they're gonna change apps from version to version, that they would please first make certain that the new one fully works at a reasonable level? It's okay that the public is effectively the 'tester' but Dev really needs to stop just 'throwing noodles on the wall' -let alone calling it a version.
Al

Al,
Well, but that's mixing responsibility with the title...
Regards.
Al