• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How Do I Access A Hidden D.net Client?

B

BiggieN

Banned
i think i asked this before but its not showing up in the search. i set a client to hidden or quiet mode. how do i access it to configure it, see if its running, etc.

another question, how do i make it autorun on startup without placing it in the startup folder? is that even possible?

geez, while i'm at it, i might as well ask another question that was asked before but is not showing up in the search as well...How do i set it to flush to the TA proxy? does the TA proxy holds packets for a megaflush or do i set it to do it myself?
 
1. At the command line, you can always type

dnetc -config

This will bring the client up in configuration mode. If you see dnetc in a Win9x tasklist, of a dnetc entry in a Linux ps -A, the client is running. When I run it silent, I like to log to a file to peek on its progress now and then.

2. Depends on the OS you are using. For Win9x, I don't think the client can be installed as a service (do a search on the words dnetc and install and you will get some hits on how to do this for other OSes.

3. Use proxy.teamanandtech.com The TA proxy does not hold packets. They flow through directly to dnet.

Good luck! 🙂
 
To make the client run as a Windows service, you can run dnetc.exe -install from the Run box on the Start Menu. This will make it run all the time, whether anyone is logged in or not, without anything in the Startup folder.

To tell if the client is running or not, you can have it log its progress and then view the log.

To use the Team Proxy, you will simply configure the client to not use a default Dnet proxy, but rather proxy.teamanandtech.com.


Details:

To get to the Configuration menu, run dnetc.exe -config from the Run box. The client will pop up with the Configuration menu in the window.

To set up the logging, go into 4) Logging Options. There are three logging options, number four looks interesting but I've never tried it.

To set the client to use the TA Proxy, from the main configuration menu chose 2) Buffer and Buffer Update Options and then 6) Keyserver<->client connectivity options. Now set 2) Automatically select a distributed.net keyserver? ==> yes to &quot;no&quot; and you will be able to fill in your own keyserver name, like this:

2) Automatically select a distributed.net keyserver? ==> no
3) Keyserver host name(s) ==> proxy.teamanandtech.com
4) Keyserver port ==>
5) Disable fallback to a distributed.net keysever? ==> yes

Note the option to disable the &quot;fallback&quot; if you want.

The Team Proxy is a round-robin setup of several proxies that all report to The Core. The proxies all flush in batches (I believe) so there could be a couple of &quot;layovers&quot; before your blocks make it to Dnet. The proxy will not hold for MegaFlushes.

Team Proxy &quot;weekstats&quot; pages
Team Proxy &quot;fullstats&quot; pages

You will find yourself on these pages shortly after you start using the Team Proxy. The weekstats pages update every halfhour on the :00 and :30 and the fullstats update on the :15 and :45.
 
Hey, BiggieN... I'll try to answer to the best of my ability 😉

A hidden or quiet client can be configured by editing the .ini or running it from command line with the option -config if you have restart on .ini change enabled that'll be enough, if you don't have it I suggest you enable it for future ease of use 🙂 To restart a hidden client run it from command line with the option -restart.

If you want it hidden, but always running and auto starting I suggest you install it as a service... again from command line:

dnetc -install (installs the client as a service it'll be completely hidden except for NT taskmanager and similar programs)

dnetc -svcstart (starts the service, but if you don't want that just reboot and it should do the same)

This will run the client even while the computer is at the login screen 🙂

Flushing to the TA proxy is best accomplished by using the round robin of pproxies in place, by flushing to:

proxy.teamanandtech.com or
proxy23.teamanandtech.com or
proxy80.teamanandtech.com

proxy23 and 80 are really only there for people that have problems connecting with the default ports, if you can I suggest you use just proxy.teamanandtech.com.

Mika's won't save your blocks for a mega flush, the one real MF we've had (last time we won the daily 🙁) was coordinated by a handful of members using irc, mail, ICQ and PM... The proxies in use at that time were and still are private, and not for public use 😉

Make sure to shout if there's anything else 🙂

With love and respect your fellow TA member

Two-Face

/edit damn you guys are fast :frown: you guys in the US should be asleep now not awake and making me look bad 😉 edit/
 
clients can be installed as services on win9x systems (see previous messages for details). It may not work as well as in NT, though. There was some debate as to whether or not they kept cracking when no one was logged on, and to whether they started cracking when someone logged back in, a few days ago.
 
sciencewhiz, I can tell you right now that they definitly keep cracking while NO-one is logged in on win2k boxes ... all of my office herd runs win2k and most of the time the machines aren't in use at all... now win9x I've only heard that it works, never tried installing it as a service there myself, but assume since so many people have done it it works 😉

With love and respect your fellow TA member

Two-Face
 
Keyserver is a personal proxy on a protected LAN?:

If the keyserver that your client will be connecting to is a personal
proxy inside a protected LAN (inside a firewall), set this option to 'yes'.
Otherwise leave it at 'No'.


(This option controls whether the client will 'fallback' to an official
distributed.net keyserver after connection failures to the server address
you have manually specified.)

Default Setting: no
Current Setting: no
New Setting --> no



that's the new client option under the fallback option. what do i do with that?
 
BiggieN, if you're using proxy(23/80).teamanandtech.com as your keyserver addy you can set that to yes, since all three of those addies are round robins of proxies that should insure that you always can connect to one. BUT (always a but😉) if you like windogg might want the added security that flushing to DNet adds (in case the comp is stolen or anything like that) you could leave it at no and if the machine then flushes from another location than yours you could get DNet to help trace it using the IP that connected to them.

I enable that setting for all my cows as none of them are in a high risk area when it comes to theft, but it's really up to personal preference 😉

With love and respect your fellow TA member

Two-Face
 
cool...i guess i'll leave it at no then if there's really no problems with it.


i couldn't access the config in startup-->run-->dnetc -config. is there something that i was doing wrong? i did not install it in the default directory btw.

and dnetc -install did not work either. did i need to have the install program in order to do that?

i'm now trying out the new client. hope it's good.

the reason i'm asking is because its been a good 2 months since i addeda new cow to the herd and i want to run this one hidden so it doesn't &quot;intefere&quot; with dialy operations of the comp. this new one is a p3 800. i'm gonna slowly transfer the rest of my herd over to the TA proxy. i've always been flushing to dnet proxies. this comp is the first one to be transitioned over. i'm doing my p3 1 gig right now so it should be flushing to TA proxy right after this batch gets done. when will my stats start showing up? i'm already a member at TA.com. do i need to do anything else? it'll give me stats based on the email addy right?
 
No problems with the fallback at either one 😉

To use the commandline options you have to run the client from the directory where it is, ie something like this from start-->run: c:\Program Files\DNet\dnetc -install (if you have the client in c:\Program Files\DNet that is 😉)

The new client is nifty, I'm using it right now... gotta love the core throughput view 😉 too bad you can't see that and have it running as a service at the same time :frown:

To see your stats at Mika's you don't need to do anything but flush through it, the stats are run every 15 minutes the weekly stats update at the hour and 30 minutes past, the full stats updates at 15 minutes past and quarter too 😉 So if you flush now you should be able to check your stats in aproximately 30 minutes (adding some due to the fact that you flush through another proxy first 😉)

With love and respect your fellow TA member

Two-Face
 
I'll just add 2 cents to claryfy : my office fleet runs on win98 exclusively (except for the file server and my PC of course). All were set with dnetc -install, all run hidden permanently, whether logged in or not. None stops cracking when user logs out. I checked that yesterday (or was it the day before) with wintop. It works, and its maintainance free.

I have logging enabled (FIFO so the logfile never exceeds 100 KB) and I can see the cpu used by the client (current and total) with wintop. The client doesn't show int task list (ctrl+alt+del). I also have a local pproxy that helps manage connections, avoid donwntime, and get some more stats 😉.
 
The biggest reason that &quot;dnetc -install&quot; and &quot;dnetc -config&quot; fail is that people fail to use the command in the proper folder/directory.

To avoid the problem, I always create a special windows shortcut to do the job. Using Explorer, open the folder that holds your client. Right click on the &quot;dnetc.exe&quot; icon, then left click on &quot;create shortcut.&quot;

Now, on the new shortcut icon, right click and choose Properties. At the end of the command line, add &quot;-config&quot; and click on OK. Rename that shortcut to &quot;Configure the Client&quot;

Do the same thing for &quot;Shutdown the Client&quot; by adding &quot;-shutdown&quot;

Do the same thing for &quot;Flush the Client&quot; by adding &quot;-update&quot;

You will end up with a very controllable client.
 
Caution, JonB : no space between minus char and the parameter, or you get &quot;Unrecognized option '-'&quot; as an answer.

-install, not - install
 
use a dos box and go to the dir that has the dnetc file. Then try 'dnetc.exe -install' or 'dnetc.exe -config'
 
Omitting the .exe should do no harm. The OS will try all executables such as .com, .exe, .bat and others I don't know.

Mind there's no space after the minus character. Also, if there's a space in the path to the client, it must be in quotes like this : &quot;C:\Program Files\RC5\DNETC&quot; -install in my case.

What was the error ? Win reported File not found, or erreo returned by the client ?
 
I tested on my own system before giving the instructions, but I guess I didn't specify to browse to the folder containing the dnetc.exe 😕 Sorry about that, BiggieN. 🙂 Sounds like you have it ironed out now?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top