PDF Server YAFPC-Appliance Forum

Hi..
I have installed the vmware version and all works fine.. but after a few days it starts asking clients for a username and password (when browseing the network). I have seen this before on our archive server (fedora core 9) but got around it by makeing it join the domain... is this possible. or what over things should i check?

I have seen this only once on a machine with a corrupted file system. The error was caused by an unaccessable "smbpasswd" file. Please try the following:

1. If the system asks for authentication for a client, type any name and any password and try to connect.

If this doesn't fix the problem try:
2. Reboot the appliance machine.

If this doesn't fix the problem try:
3. Make a backup. Then remove all partitions of the HDD. Reboot the latest CD image YAPFC-504.iso and allow repartitioning of your HDD. After the system is up and running, try to access it from some client pc. If this works, restore your backup and activate your license again.

Have fun

W.U.

Ok...

first thanks for reply...

It seems to happen over night.. so i left it one day and low and behold it asked me for a password in the morning..

so following your advice i typed random stuff into username and password box and it let me in..

i also know that a reboot works... as i did this earlyer..

so if it is a courupt smbpasswd file how do i fix this.?

You can't "fix" this file. It's a Linux life system and all those files are hold in RAM. So a reboot will fix it automatically. The interesting question is: why is it corrupted? In versions prior to 5.02 there was a bug causing corruption when many users make their first access at the same time. But this should be fixed in later versions. If you run a recent version (at least 5.02 or above) it should not happen again. We should keep an eye on it. If it happens more often please report your version, the number of users accessing the appliance and the average number of documents created per hour.

ok cam in this morning and tested it... once again it asked for a user name..

intrestingly on network neibourghhood i can access it using IP 10.100.30.15 but not its name bgpdf

"\\BGPDF is not accessible"
"Access is denied"

but i can nslookup both name and IP..

info
ver = 5.04 trial (no lience)
Disk Usage: Size 711M, used 32M, avail 643M, usage 5%, uptime: 09:06:21 up 1 day, 22:41, 0 users, load average: 0.00, 0.00, 0.00 , total documents printed: 4

IP 10.100.30.15
mask 255.255.254.0
gateway 10.100.31.254

at present only one user (testing before a buisness managment meeting wher i should get the go ahead to purchase)
windows network is a 2003 domain
the client PC is 2k sp4
and yafpc is a virtual machince running on vmware "virtual infrastructure 2.0.2"

as a test i am going to create a dhcp resavation and set it back to dhcp rather than static...

another thing it seams to sit at about 30% cpu useage when idle... is this right

reboot fixes it once again.. will check every 12 hours

ok... monday morning... and access by name bgpdf is access denied.. but ok via IP...

My problem in this case is: The appliance _always_ asks for username and password when being accessed. But the default behavior for Windows is to give it the logged-on user and his password-hash without asking for. The appliance then accepts _every_ password-hash without checking it and recognizes only the username.

There are two possible reasons for "asking the user for credentials":

1. The appliance isn't able to accept the user or "every password". This could be caused by a corrupted file system (in RAM of the appliance, e.g. "smbpasswd" file).

2. The Windows system denies giving the credentials to the appliance on request.This might be caused by some "local policy" or something like this.

My recommendation:
Setup a clean new YAFPC-Appliance machine with the latest version (5.04) CD image. Don't use the same hardware as for your running system and don't use a backup of your settings. Setup the network and one printer on it and test it for some days. If it behaves like the running system, the reason is most likely located in your Windows environment. If not, the reason is in your current appliance machine. Then we should try to find out more about it.

Have fun!

W.U.