Help! Client trys to dial when set for LAN proxy!

[MWalkden]

I installed some clients on a lan and set up a proxy. Some of the PCs have modems and on those units the client trys to dial-up instead. The ones without a modem work fine. What am I missing in the INI?

 

[ViRGE]

It would be the "interfaces to watch"; but I wouldn't know what to set it to.😱

 

[LeBlatt]

Do you have the lines

[networking]
keyserver=yourpproxy
autofindkeyserver=no

??

 

[MWalkden]

LeBlatt, yes, keyserver=my local IP address: Port and autofind=no. Also have no fallback=true.

I will look at the interfaces to watch setting and see what it has to offer.

(/edit to fix smiley made with : and P in port /edit)-grrrrr!

 

[MWalkden]

Here is the INI just for further reference:

[parameters]
id=rc5crackheads@hotmail.com

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

[rc5]
fetch-workunit-threshold=160
preferred-blocksize=33
randomprefix=27

[networking]
autofindkeyserver=no
keyserver=192.168.2.102:2064
disabled=no
nofallback=true


[buffers]
buffer-file-basename=buff-in
output-file-basename=buff-out

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

 

[Poof]

Some of the PCs have modems and on those units the client trys to dial-up instead. The ones without a modem work fine. What am I missing in the INI?

I don't think it's an ini problem. I think it's a network configuration problem. This is assuming that all the machines have NICs (and as you noted, some have modems too). Looks like TCP/IP is binding to the "dialup adapter" (on those with modems) rather than binding to the NIC.

You might want to check that to confirm, ie., take the modem entry out of the Network properties of one to see what happens. (this is of course assuming you are running windoze)

 

[MWalkden]

Poof, that sounds like a good idea. 2 of the units are ME and one is 2K. I have found that in one of the ME's and the 2K it only did it the first time and now appears to be working. I still have an issue with the other ME. The lan is operating without a gateway defined (it is blank on all units including the 2K server). This may be part of my issue and probably has something to do with DNS and active directory. On the remaining ME box the dial-up adapter is bound to client for MS networks and TCP/IP but not to file and print sharing.

A theroy is that the routing table is adjusted when a dila-up occurs and unless network activity occurs after a dial-up session it is defaulting to the dial-up TCP/IP route. If this is the case then the other units may have a problem after a dial-up occurs and no other LAN activity occurs before the client tries to flush again.

ME allows you to specify which TCP/IP is default, but 2K relies on something else to make that determination (I don't know exactly what). I will check what is set to default in the bindings and monitor the activity for a while. Maybe I should define a gateway for the LAN too.