J
James McGuire
My company has a server with a public-IP, for example, 206.214.62.55,
but it is not connected to the Internet. It is advertised on public
DNS, but the only connection to it is via a T-1 on a private network.
My issue is that when I try to access that server, my ISP resolves the
domain name to the 206.214.62.55 address, but doesn't have a route to
it - so it fails. All expected.
What I need to do is setup a static route on my XP machine to point
all requests for that IP at a gateway address of, say, 66.92.237.18
for example. That is the IP for a public router that I know has a
good route to my server.
Essentially I need to setup my own routing rule locally on my machine,
since my ISP doesn't have a good route. Is there any way to do that?
Thanks for any help..
but it is not connected to the Internet. It is advertised on public
DNS, but the only connection to it is via a T-1 on a private network.
My issue is that when I try to access that server, my ISP resolves the
domain name to the 206.214.62.55 address, but doesn't have a route to
it - so it fails. All expected.
What I need to do is setup a static route on my XP machine to point
all requests for that IP at a gateway address of, say, 66.92.237.18
for example. That is the IP for a public router that I know has a
good route to my server.
Essentially I need to setup my own routing rule locally on my machine,
since my ISP doesn't have a good route. Is there any way to do that?
Thanks for any help..