We are using a fibre line here, we don't use PPPoE. What I ment by the
internet statement was, if we were having problems with our PPPoE which
we don't have, the users wouldn't be able to connect to the Internet
either. They would have the same connection issue.


Robert Aldwinckle wrote:
"Tim Kendall" wrote in message
...
Hi Robert,

It's not a problem with our PPPoE because both of our terminal servers
are running this but only one of them is encountering this issue.


I don't think that that is a sufficient argument against the idea
because unless you trace them both you know nothing about
any timing differences between the machines.


Also the users could be using the Internet on non-cached websites
with no problem at all.


Explain?


As for the ipconfig /all, we have policies on the user
side setup that won't allow users to run a command window

but once again connection to the outside world is already established.


That's precisely my point. With PPPoE you may think that there is a connection
but there may not be at least temporarily and if that is when an app is checking
for a connection it will show that there isn't. From there the associated external
symptoms would be simply a question about the usability the app provides
for that case.


We send/receive e-mail internally on our server through a separate
account then used to email outside suppliers/customers, and never needs
to access the outside world.


So what? Does that imply a second networking path? E.g. not PPPoE?


Robert
---