Wrong. If telnet from the host is not working, it isn't the PM and it
is the same problem breaking Radius. You've jumped to a conclusion too
fast.
>I then took all the IP addresses my machine listens to down (I am hosting
>a bunch of other domains (for www purposes), which is done by making your
>machine listen to different ip numbers...)
>I then tried it and YES, it worked!!
>I then, one by one, up'ed the ip numbers again, checking after each one
>if the ping/telnet'ing still worked, and sure enough, after each it did,
>and it stil does.
Bingo, it was your *host*.
>have to be concerned about the functionality of the terminal server.
>This is supposed to be one of the market leaders. This kind of
>un-logical behavior should NOT happen.
I completely disbelieve we caused it though any fault of ours. It sounds like
your host was screwed and resetting the IPs cleared it. I've seen that
happen before, and it is something on the host messing up, not us. And
if it was a routing update problem, then someone is using the wrong IP or
entered a bad static route, there is nothing we do that would spontaneously
cause it without a human error.
-MZ
-- Livingston Enterprises Technical Support Phone: 800-458-9966 FAX: 510-426-8951 support@livingston.com <http://www.livingston.com/> 6920 Koll Center Parkway #220, Pleasanton, CA 94566