I am afraid that does not work. The client, by definition, connects to the
gateway machine via the LAN. The dial-up settings in the clients Internet
Connection Options are therefore disabled and thus not settable.
Peter Hallett
> Open up Internet Explorer on the 'client' machine.
>
[quoted text clipped - 13 lines]
> > thing is to leave the Internet permanently connected when the client machine
> > is on. Pretty obviously, this is not acceptable.
> I am afraid that does not work. The client, by definition, connects
> to the
[quoted text clipped - 26 lines]
>> > --
>> > Peter Hallett
I would look on the client to see what is calling the Internet. It might
be a legitimate program that is trying to check for updates and
therefore overriding the normal settings, or it might be malware. Use
the Task Manager to see what is running. Try a clean boot with msconfig
on the client. Let me know if you need help in checking for malware.
Malke

Signature
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
Peter Hallett - 30 Apr 2005 12:31 GMT
I am sorry if this is a very late reply to your response to me of 2/28/2005
but I have been conducting a number of tests since then and repeating them a
sufficient number of times to be sure that my conclusions are correct.
The result is that neither the gateway nor the client computers can be
prevented from dialling the Net unbidden - at least not by using any setting
that I can find or has been suggested by other correspondents. It seems not
to matter that the gateway is set to never dial a connection. The client
machines and the gateway machine itself simply dial up whenever they feel
like it. I have disabled Windows automatic upadates but nothing, it seems,
will prevent the auotdialling. That is actually quite serious. Anyone with
an unattended computer left disconnected to their pay-as-you-go dial-up
Internet service could return to find themselves connected and with a
substantial 'phone bill.

Signature
Peter Hallett
> > I am afraid that does not work. The client, by definition, connects
> > to the
[quoted text clipped - 34 lines]
>
> Malke
Interrogative - 30 Apr 2005 12:53 GMT
>I am sorry if this is a very late reply to your response to me of 2/28/2005
> but I have been conducting a number of tests since then and repeating them
[quoted text clipped - 6 lines]
> that I can find or has been suggested by other correspondents. It seems
> not
Sorry - untrue. You can set the connection on the main computer to NEVER
dial a connection and you can set the connection sharing to disallow control
of connect/disconnect to clients from the main machine. In that way, you
manually connect at the main machine and the rest cant affect that in any
way.