• 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.

Dnet client and Win 98SE ICS

V

Viztech

Platinum Member
I need to set up ICS for a buddy who is running OGR and RC5 for me. The ICS server is on a 56k dialup. We were running remote buffers at his place at one time, but would it be best to flush the ICS client machine directly?

I thought that I read once where ICS only opens the common ports, so do I need it to go to a Port 80 proxy?

viz
 
I am using ICS over dialup and the only way I could get rc5 to flush was using a pproxy on the ICS machine and flushing to there, and from there, the world.
 
I'm using ICS over dial-up and the DNet client connects fine on all the machines on my LAN...I do a manual connect though on all the computers...no shared buffers or anything like that.
 
Sukhoi-
You maually connect? Through the standard port 2064?

PF-
I'm sure that the Pproxy would be the ideal, but is not an option here. 🙁

I'm thinking that I'll just revert back to remote buffers, or have that machine dialup the net once in a while.

viz
 
Hi viztech, I have one machine that is on a cable modem with two NICS the second NIC plugs into the home LAN and provides ICS services. Two boxes are set to flush to the TeAm's RR-Proxy. Once I got those machines working on the LAN and talking on the Internet via ICS, then I did nothing special to get them to flush/fetch with RC5. I do not run a pproxy on this setup. The RC5 systems have non-routeable IP addresses, so they are definetly using ICS to make the connection. In your case you would need to set ICS to dial-up on demand and get it working properly with then Internet. I have had problems with ICS taking too long to establish the dial-up connection and the client times out. Thus, I'd consider using pproxy. I do that on another setup and it works fine. The main box has pproxy and SetiQueue running. Once in a while I have a problem, but for the most part it works well.
 
The problem with using ICS is that the remote clients might be set to use the network connection feature. If you have ICS to setup to dial automatically, then every time your client goes to flush, it will start looking on the netwrk which will cause the ICS machine to dial autmoatically. 🙁
 
Yes, I'm connecting to the TA Round Robin. Haven't specified a port, so I assume it's 2064 or whatever.

Here's what I do to flush:

Sign online with the ICS comp. Open up DNet on the ICS comp and select update. Then I do the same thing on my other clients. Works just fine for me. 🙂

Never tried to get DNet to dial in automatically.
 
OK I'm understanding the situation much better now. The client will cause ICS to dial whenever it wants to flush, so with the standard settings this will occur at times. If the ICS server is off-line, the client would start on randoms thanks to that change in the Dnet client a while back that will make the client crack everything before trying to initiate a connection. 🙁

/me thinks that I'll just stick with remote buffers on the client, and dial-up detection on the ICS server. 🙂

Thanx
viz
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top