Ok we need specifics...<br>
Do you have Proxy server running?<br>
RAS?<br>
What's on the machine? Services, Programs etc.<br>
I guess its a Server???<br>
<p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>
WE have advanced server and do not have proxy set up on this machine. It is a small office and have only setup to share the modem on the server and have done nothing else. We have only two lines and are not able to dedicate a line for the computer. When I try to doing anything in RAS it like to answer line two and we can't afford to not be able to answer line two as phone call. We are having DSL installed in our office in about two weeks to help open up a line.
Have not used Advanced Server<br>
Did just finished DSL though<br>
There is a thread a week or so back on that.<br>
<br>
A third phone line is far cheaper than DSL!!!<br>
DSL is nice and very fast but it's not cheap.<br>
<br>
<p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>
It sounds to me like there is something on the network triggering the dialer. If you are using ICS (Internet Connection Sharing) this could be a number of things. What usually happens is an application or other service tries to find resources not on the local network so it triggers the dialer. It could be somebody with AOL Instant Messenger running in their task bar, ICQ, or something set to get live updates on a schedule etc. <br><br>There are a number of ways to pinpoint the cause. You could install a program called EndItAll on all of the workstations then execute at each worstation (its a freeware program, check ZD Net). Go to the server and disconnect the modem and then see if it tries to dial. Another way would be to shut down all of the workstation and turn them on one at a time until the dialer triggers. Then you can pinpoint the source.<br>Generally something as simple as pinging an IP address not on the local network can trigger a Demand Dialer. <br><br>To take it a step further, if you were savvy with a network sniffer you might be able to pinpoint the source. Im not that familiar with them so I can't help you much.<br><br>Good luck.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.