ICS automatic connect

[glubbsch]

I am running a small network with 3 computers running WIN98SE, ICS and outpost.
ICS is working fine so far.
The problem I have is, that the clients automatically connect to the Internet through the server when outpost is running.
This is happening although I don't want to be connected to the Internet.
Without outpost I am only connected when I call a web-site through my browser, which is fine.
Is this a wrong configuration or a bug?
Thanks for any suggestions.
glubbsch

[root]

How are the clients connecting to the internet? Do you mean a browser starts up?

[chrisclu]

Hi glubbsch
Welcome to the forum. I ask too, what do you mean by clients connected? If browser started like Root asked, there is a serious problem. If what you mean is that you see the client stations in a listening mode, that is much different and of no concern as it is not a connection. The clients are just members of ICSs little network and the "channel is open" as in "Internet Connection Sharing"
Chris

[glubbsch]

What I meant is, that the server starts dialing and the phone bill is reaching enormous dimensions.
The browser didn't start up, but as I said, there is an dial-up connection, which stays forever (It was for longer than 5 hours until I noticed it), although I configured the dfue network to hang up after 5 minutes without activity.
Any ideas?
glubbsch

[root]

I don't understand why you think its your clients if you Outpost on the server. Anyway, if its Outpost, then it is trying to check for an update automatically.
Go to help and uncheck the check for updates automatically. That will fix it if its Outpost doing the dialing.

[bassbag]

hi again root..
Outpost hasnt got a facility to auto dial/connect to the net has it?.It just has auto update when a connection has already been made hasnt it?.Sounds more like some sort of spyware /dialer to me to be on that length of time.
me

[root]

To tell the truth, I don't know.
A dialer had crossed my mind, but it seemed to be when he installed and ran Outpost only. He said it didn't happen when Outpost wasn't running.

[chrisclu]

It is possible that OutPost is trying to do an auto update ( which is web) while you have auto dial selected in your options. If you also have (I am trying to remember dial up service) remember my id and password, There would be nothing to stop the dial up. At least uncheck the password. It is a hassle to input it all the time, I know, but at least in your case it would be cheaper:D
Regards,
chris

[muchod]

Also, Outpost can be trying to resolve ip addresses to display in the logs. Select 'All Connections' and use the right button in the log display, and go to Columns->Advanced->Resolve and get sure 'If in cache' or 'Never' is selected.

Regards,

[bassbag]

There is no autodial in outpost (mine anyway) , but as Chrisclu said its possible that he has tools>internet>options>connections>that dial whenever a network connection is not present is ticked?.Also in Outlook express>options>check for new messages may be ticked>and if the computer isnt connected at that time >it may be ticked to connect.I can see how outpost would would want to auto update , but not now how it can actually dial.I think that would be IE or OE settings or a dialer/module.
me

[glubbsch]

I forgot to mention, that I have outpost installed on all the networked computers. Can this be the problem?
Is it sufficient to have outpost on the ICS server?
By the way I don't have any auto-connect activated in my browser or outlook, because evrything is fine without outpost.
glubbsch

[root]

Having Outpost on all computers should be ok. When does your server connect? Is it at bootup?

[glubbsch]

The server connects (start dialing) as soon as the client finished boot up.
glubbsch

[root]

OK You have a network with 3 computers.
You have Outpost installed on all three.
When one of the clients boots up, the server tries to dial the internet. Does both clients trigger this or just one?
If you stop Outpost, this doesn't happen. Which Outpost? On the server? On the client?
If you let it dial up, can you check the allowed log real quick and see what app is connecting to where?

[glubbsch]

I have outpost installed only on 2 of the 3 computers.
On the server and one client the outpost version is
outpost freeware 1.0.1617.1854
When I check the allowed log I don't see a specific application connecting. What would you expect to see in that log?

[chrisclu]

Here's an example of an allowed log.
Chris

[root]

Clear all the logs in Outpost by going to tool>clear all log information.
Now start your client computer that dials up. Let it dial up and connect, wait a minute but dont initiate any action yourself. Next get a screenshot of the allowed log like Chris's picture, and let us see what it looks like. I don't know what I'm looking for, but may recognize something suspicious.
Also, while your booting the client and letting the dialup start, if you could, watch the main interace of Outpost with all connections expanded so you can see whats going on there.

Now, new topic. You say you have the free version. Is that on the client? You do have the pro version on the server computer, right, with the clients IP in the trusted zone? If not, how are you making this work?

[Danil]

What I meant is, that the server starts dialing and the phone bill is reaching enormous dimensions.
The browser didn't start up, but as I said, there is an dial-up connection, which stays forever (It was for longer than 5 hours until I noticed it), although I configured the dfue network to hang up after 5 minutes without activity.
Any ideas?glubbsch, this has no relation to Outpost.

Outpost is unable to run your dialer without your knowledge.

When autoupdate is turned on in Outpost then Outpost will start the dialer. This dialer will appear on top of all your windows - so you won't miss it. Then you should click Ok in the dialer. Only after that it will start to dial.

Guess, you should check the settings of your program - possibly some of them has autoupdate turned on. Also check your PC for malware.

[glubbsch]

Attached is a picture of the log after the client has dialed.
I have the notebook (client) in the trusted zone.
I checked my computers for malware.

@danil: The behaviour I describe only happens with outpost activated!!

glubbsch

[root]

I don't see anything there that would dial. The only thing I can think of now, is if the ICS manager doesn't see a connection, then autodial kicks in. :confused:
I don't know, just a guess. The thing is if it only does it with Outpost running, but Outpost itself cant do it, then something is being enabled by having Outpost loaded, that is not enabled if Outpost is not loaded. :confused: :confused:

[muchod]

Originally posted by glubbsch
Attached is a picture of the log after the client has dialed.
I have the notebook (client) in the trusted zone.
I checked my computers for malware.

Have you changed the 'Resolve' setting to 'Never' or 'If in cache' ?

[glubbsch]

That's it.
I change this settinng and everything is fine.

Thank you !!!

To understand it, what is this setting for and why do you think it made my server dial?

[muchod]

Originally posted by glubbsch
To understand it, what is this setting for and why do you think it made my server dial?

Outpost is trying to resolve (convert the ip address to a name) your lan internal ip adresses to show the name in the logs because it was configured to allways resolve. Altough you set the name in the HOSTS file it will shot the RAS dialer.

I told you some messages ago ;)

Regards,

[lpsi2000]

Hey guys,

One more thing to keep in mind with dial up connection. When it is configured to dial when a internet activity is requested, it will dial no matter what application requested the service. That will include (outpost, NAV live update, spyware, trojans, etc..).

glubbsch, keep your eyes open because you could have this issue with other applications.

[chrisclu]

Good thinking Muchod:):)
I just put some salt on some fried almonds in your honor:):)
I'll think of you as I enjoy them:D:D
Chris

[muchod]

Originally posted by chrisclu
I just put some salt on some fried almonds in your honor:):)
I'll think of you as I enjoy them:D:D


Sure Chris,
But you will enjoy this ones a little more than me ;)

[jonrkc]

Let me just dip my cyber-toes in here long enough to express hearty thanks to the writers in this thread for solving a problem that had baffled me.

I was experiencing repeated mysterious attempts to connect to my ISP, after installing Outpost (free). I thought I'd disabled every feature that could be doing that, but thanks to the writers here, I was able to go into the Help menu and disable "automatic updating" and into the logfile and select "Never" under "Columns>Advanced" for DNS resolution, and since then there has not been one attempt to connect. I ALMOST feel secure enough to put my connection back on an "automatic" basis.

I think some of the features of Outpost's GUI are pretty non-intuitive, but I am impressed by how well and transparently it works, apart from the little problem I had. I was using ZoneAlarm with great satisfaction till the latest version came along, which proved totally impossible to live with. I hope Outpost will be a long-term solution now.

Thanks again, everybody!

Jon R.
Kansas City, Missouri

[chrisclu]

Hi Jon,
Welcome to the forum.
That was some "toe wetting":D
Thanks for writing. We can now just copy and paste your reply for the next poster who has the problem:):) Don't mean to put you on the spot:D - we'll probably just link the thread.
You think you like Outpost now?? Just wait till Version 2 :):)
Thanks again,
Chris