The Share name is PUPSERVER and the share is automatically created by Pupserver and is named usr=root passwd=woofwoof. I named it that to make it obvious what the username and password are.

it's still not working for me...

i'll try to post a screenshot... .

Hi Jason,
I presume you clicked on "Windows Network" in the Network Browser and didn't see Pupserver?

Perhaps I have made a mistake in naming the share usr=root passwd=woofwoof. Can't imagine why I left that space in the middle. Here's what to try:
Go to /etc/opt/samba/smb.conf which contains:

Code:

# Share
[usr=root passwd=woofwoof]

Change the share name to usr=root_passwd=woofwoof or anything else that doesn't have a space in it and save. Then open a terminal window and type

Code:

samba restart

Then go back to Ubuntu or Debian, refresh or restart the Network browser and see if you can connect to Pupserver.

Best of Luck, J

Sorry that i haven't posted back on this in a while, been really busy lately

I think i may have to throw in the towel on this one.. i dunno.. but i still can't seem to be able to get anything to work...

i've tried again today to connect to pupserver without much luck..

i tried the advice (above) as jrb suggested , changed :

Code:

usr=root passwd=woofwoof

to:

Code:

root

so pretty much made that part as simple as can be..

then opened a terminal and :

Code:

samba restart

although i get a weird error and don't know if it means anything or not..

Code:

killall <something> unable to kill pid <somenumbers>

i'm sure samba has to be running , if i use "top" from the terminal it shows a few entries for samba..

so then from my crunchbang laptop (connected as ethernet and not wireless to the same router as the pupserver machine) i have nautilus , i choose "connect to server" as suggested/explained by rcrsn51, but still it's a no-go..

so then i thought about puppy having pnethood, so from this same laptop i fire up a live puppy (dpup actually) , open up pnethood, it runs and does it's thing , and:

Code:

no server found

from a browser , if i open the config page for my router (10.0.then.the rest) the router shows "PUPSERVER" in it's list of connected devices..

but as for actually connecting to pupserver from another connected machine?? it's like PUPSERVER isn't even there at all...

Hi jrb, Pupserver 435 is just what I was looking for. Within 3 minutes I was able to boot from PS435 live cd and make all my files and music available to the rest of the family. Nice job. Thanks.

I am also hoping to use this as a PXE server to encourage the rest of my family to trial Puppy. It seems to work ok (I have tried it with various puppies and several machines with some failures, but mostly successes) but the main problem I am having is that the PXE client cannot access the internet after booting unless I take the Pupserver PC offline. (I tried running the internet connection wizard and it goes through the auto dhcp routine correctly but still won't allow access to the internet till I shut down pupserver). Have you experienced this?

I tried installing the dnsmasq and server3 pet mentioned by gcmartin but I had problems with it and wondered if it was conflicting with the tftp server that was already in the PS435 network menu. Also, that other method uses the /tmp folder to hold the netboot folder and initrd etc, whereas the inbuilt tftp server in PS435 seems to use /root/tftpboot for that purpose. I figured I should try to stick with the inbuilt server method.

Is there maybe some simple way to stop the PXE server rather than shutting down? (although that requires a manual intervention for each PXE client attempt..)

I have found some topics that seem related to my problem but its a bit confusing and I wondered if you had a clear recommendation how I should proceed.

Hi greengeek, I haven't used PS435 in a while, my old P2 fileserver died and I've been using a screenless Lenovo S10 lap top with external monitor as my fileserver, printserver and main internet machine. Its running Dpup Exprimo with SambaTNG. Likewise I haven't played with PXE for a while either.

Hopefully I have some PXE ready puppies handy and I can work on your problem. It won't be until tonight though so I'll get back to you.

The TNG version of Pupserver gave me the same problem that you describe, PXE boots won't connect, wierd.

Hi jrb - thanks for trying that. I will give the other iso a trial. (I previously found that the gcmartin method would not boot one particular laptop I have, whereas the inbuilt netboot server in 435 did manage it, so I will try it again with the other iso and see if the result is the same).