Problems with dnet v2.8010.463b & pProxy

[BGod]

I know we talked about this a while back, but I'm having problems after downgrading 9 machines. They don't see the pproxy anymore and will only fetch/flush if you manually force them to do so. Any ideas on how to get them to keep some fresh hay on hand?

Here's the .ini file:
[parameters]
id=bgodfrey@dia.net

[buffers]
allow-update-from-altbuffer=no
frequent-threshold-checks=3

[misc]
project-priority=RC5,OGR=0,CSC=0,DES=0

[triggers]
restart-on-config-file-change=yes
pause-on-no-mains-power=no

[rc5]
fetch-workunit-threshold=4096
randomprefix=9

[networking]
nofallback=true
autofindkeyserver=no
keyserver=192.168.0.3:2064
dialup-watcher=active
interfaces-to-watch=*

[display]
progress-indicator=off

 

[sciencewhiz]

Are you running win2k? I had the same problem and it went away with versions 11 and 12. I never found a solution, but if I remember correctly the older clients worked.

you might try 462 from dnet's ftp or any of the earlier clients.

 

[Jator]

Jeff,

Why do you have the dialup watcher active when you are connecting to your private pProxy?

Jay

 

[BGod]

I've got 3 Windows 95 machines at work running hidden. There is no good way to get them to flush because there is no Task Scheduler. I don't want to have to babysit them again.

Jay, The dial-up-watcher is active so it can find a connection. The next line tells it to look for any open connection (i.e. eth0, ppp0, etc). For some strange reason they are still not finding the connection.

My home heard, 4 Win98se, 1 Win95 & 1 Win2K, are doing the same thing. They just can't find that they've got an Ethernet connection to the pProxy. All of those machine now have a scheduled task to: dnetc -update at 5pm each day.

I've even gone as far as to delete the .ini file and then run: dnetc -config in a DOS box thinking the .ini from the newer client was messing up the older client. Extra parameters that weren't supported in older versions. Still won't connect. 🙁

 

[Viztech]

Jeff-

Get rid of the dial-up watcher=active and the interfaces to watch.

viz

 

[SpaceWalker]

Yo ßGød

Here is the .ini form one of my work comps:

[parameters]
id=jjrivera@bellsouth.net

[rc5]
preferred-blocksize=28
fetch-workunit-threshold=5
randomprefix=4

[misc]
project-priority=RC5,CSC=0,OGR=0,DES=0

[triggers]
restart-on-config-file-change=yes
pause-on-no-mains-power=no

[display]
detached=no
progress-indicator=abs

[networking]
nofallback=true
autofindkeyserver=no
keyserver=192.168.0.1:2064
dialup-watcher=active
interface-to-watch=*

[logging]
log-file=5004us.log
log-file-type="no limit"


They all flush to my computer which is running the pProxy...
this is the same .ini they are all using...except for this line...
log-file=5004us.log it's so Cow Control can keep track of them....


MOOOOOOOOOOOOOOOOOOOOOOOooooooooooooooooooooooooo..................

🙂

BTW...nice Dump today.....

 

[BGod]

Jay nailed it on the head! 🙂

As soon as I took out the dialup-watcher the darn things just started gushing. 😀

Viz, I haven't decided what the runner up gets yet.

SpaceWalker, Not half as nice as your dump for Tuesday! 😛

 

[SpaceWalker]

YO ßGød...
I waited until pass 7 PM so you could come in FIRST on monday...


MOOOOOOOOOOOOOOOOOOOOOOOooooooooooooooooooooooo................

🙂