Need help quick!

[CetiAlphaV]

I have the opportunity to assimilate about 150 - 200 comps. The problem is that the client won't autodetect the core. Since the client won't detect the core I can't get any blocks. Is their anything that needs to be installed on the comps to help the client detect the core. I want to install the client as a service and these are all win95 machines. It says that it can't resolve name "proxy.teamanandtech.com".

Please help.

 

[Russ]

CetiAlphaV,

What processors are in these systems? Even when the client won't auto-detect the core, it will go ahead and crack by guessing the best core to use. It just takes a little longer to fire up.

As for the team pproxy not resolving, are you behind a firewall? Can you ping or traceroute it from one of the machines?

If it is a firewall issue, you can try pointing it at one of the pproxies in the RR that has port 80 open. Here is the list.

Russ, NCNE

 

[Joe O]

Try changing proxy.teamanandtech.com to proxy80.teamanandtech.com and shutting down and restarting the client to pick up the change.

 

[CetiAlphaV]

The problem with selecting a core specifically is that they processors range from Original pentiums to Pentium III's and celerons.
When I try to ping anyone I get "unknown host rc5.casefinder.com" same thing for www.yahoo.com and proxy80.teamanandtech.com.
Here is the update screen.
distributed.net client for Win32 Copyright 1997-2000, distributed.net
Please visit http://www.distributed.net/ for up-to-date contest information.


dnetc v2.8010-463-CTR-00071213 for Win32 (Windows 4.0).
Please provide the *entire* version descriptor when submitting bug reports.
The distributed.net bug report pages are at http://www.distributed.net/bugs/
Using email address (distributed.net ID) 'crackinfool@yahoo.com'

[Jan 20 19:53:23 UTC] Network::failed to resolve name "proxy.teamanandtech.com"
[Jan 20 19:53:23 UTC] Network:pen Error - sleeping for 3 seconds
[Jan 20 19:53:26 UTC] Network::failed to resolve name "proxy.teamanandtech.com"
[Jan 20 19:53:26 UTC] Network:pen Error - sleeping for 3 seconds
[Jan 20 19:53:29 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Jan 20 19:53:29 UTC] Could not update to/from the net. Network down?

I get the same thing even when I specify a core, and when I try to use port 80.

 

[IsOs]

How's your machine connected to the internet? Looks like you're behind a software firewall or you're using an internet sharing software. Find out your exact network connections for the internet so we can advise you correctly.

 

[CetiAlphaV]

I'm on a LAN that uses netware servers and bordermanager for it't proxy software. I hope that helps.

 

[Russ]

CetiAlphaV,

Add the following to the ini file of one of the systems, restart the client and see what happens:

[networking]
autofindkeyserver=no
keyserver=204.209.128.157

I'm thinking this might be a DNS issue.

Russ, NCNE

 

[HomerSapien]

Wow, that is some herd you will get.. Good Job!!!

 

[Slahr Dzhe]

I agree with Russ.

I think this is a DNS issue on your network. :frown:

SD

 

[CetiAlphaV]

That worked.

Thanks guys for your help.

 

[CetiAlphaV]

Yeah it will be pretty nice. I can't wait to get them all cracking.

Do you guys have any recommendations on how to remote admin them.

 

[RaySun2Be]

DOH! Too slow today. :Q

Do you have a PC that has an Internet connection? If so, check your LAN settings, note the proxy server IP addy, and what port used (usually 80 or 8080)

Also, it sounds like you are mixing two issues, the CORE selection has nothing to do with the network issue.

Several things to try to resolve the network connection issue, which sounds like a firewall problem.

1. Try using the IP address of the proxy80.teamanadtech.net proxy server in your .INI file:

[NETWORKING]
keyserver=xxx.xxx.xxx.xxx:80

2. Using the settings found in your Internet Browser for the firewall, add the following settings to your .INI file:

[NETWORKING]
keyserver=xxx.xxx.xxx.xxx:80
firewall-type=http
firewall-host=xxx.xxx.xxx.xxx:80

where the firewall-host "xxx" = the IP address of the firewall (you can use the DNS name if that is what is used in the browser), the ":80" = the port (use the one in the 'Net Browser)

you can also use the command line DNETC -CONFIG to get into the configuration options and try different settings under the Buffer Options selection.

Good luck, make sure you have permission to install the client, and keep us posted on any issues or progress.

 

[CetiAlphaV]

Yep, I already got permission but I don't exactly have tons of time to get them all setup and cracking. So thats why I needed to get this figured out quick.

Once again thanks your help.

 

[Russ]

CetiAlphaV,

We love you, man!

Russ, NCNE

 

[dawks]

Cool.. I guessed DNS too when I read over.. I am learning lots from here!

 

[Russ]

<< I am learning lots from here! >>



DaZ,

And that, in a single sentence, is the definitive answer to the question, &quot;why?&quot;

Russ, NCNE

 

[RaySun2Be]

Amen Russ! I've learned tons being a part of this team, and I am still learning!

As far as remote management of WIN95 clients depends on how much access you have to the network servers. if you are an Admin, and can modify logon scripts, then you can write an install script something like this:
- checks to see if the dnet folder already exists
--- If it does exist then bypass install
--- If it doesn't exist then
---- Create the dnet folder
---- Copy the preconfigured dnet files
---- Run dnetc -install
---- Run dnetc -scvstart
- Exit

This is only one way, I'm sure some of the brighter bulbs around here have figured out other ways too.

For that many workstations, you might also think about running a personal proxy server that would then require only one connection going through the firewall that would keep the entire work herd fed, and there are stats programs available that can help track the output by PC name or IP address based on the perproxy log files. Also it can store blocks for the entire herd so if there is a network problem connecting to the internet, the entire herd can be fed good blocks by the perproxy for several days until the connection is stored.

I switched to a perproxy at work, and it has simplified and reduced the time I spend managing the herd. There is only 1 PC I need to deal with if the key server IPs or DNS names change, I can buffer enough blocks for the entire herd to account for several days of &quot;downtime&quot; if needed, and I can track the output of the entire herd by IP address, and can get my own work herd &quot;stats&quot;!

Way to go on the assimilations!

 

[crYnOid]

for machines that are running win2000 or NT try rscc. i have found it to be ver helpful.