J
Jerry Boyer
This is the first time I've tried such a means for
assistance. I've struggled with the fact that what I'm
attempting to do seems like it should be fairly easy and
straightforward, yet experience tells me otherwise, so I'm
hoping someone out there who has "been there and done
that" can give me a hand.
We're a growing small family-owned business. As such a
few here work a lot of hours and would like to have the
flexibility of working some from home. Yet, I have not
been able to make this happen and have found very little
guidance from any Internet resources.
Here is our network configuration: NT4 (SP6) server which
does it all, including the following: application server
(we run a few acquired and home-grown apps), data server
(we centrally manage - backup - most our data here), e-
mail server (Lotus Domino), Internet server (we all access
our satellite link from here), proxy server (Microsoft's
2.0 - originally this was setup to enable sharing a dial-
up connection to the Internet, yet it is still in place
for security reasons, essentially functioning as our
firewall), DNS (we use static IP addressing internally -
primarily because we could not get DHCP to work
initially), and antivirus server (Norton).
I realize this may seem like a lot for a single NT server,
yet it has served us well - remember we're a small
business - and we've not encountered any performance
problems.
So, my question is what is the simplest, most effective
way to remotely connect to our NT server from a Windows XP
client? And more importantly, in detail, how do we do it -
what are the precise steps? As I alluded to above, I
have tried this via Lotus Notes to simply exchange e-mail
and also tried to access the entire network. Currently,
from my XP client, I get the following error: "676:
remote phone is busy". I have also tried connecting from
my Windows 98 client at home and while I appear to connect
successfully, I'm not able to see or do anything. While
these issues may be easier to resolve, remember I'm
interested in a complete solution - one that will
circumvent any other issues I may run into eventually.
assistance. I've struggled with the fact that what I'm
attempting to do seems like it should be fairly easy and
straightforward, yet experience tells me otherwise, so I'm
hoping someone out there who has "been there and done
that" can give me a hand.
We're a growing small family-owned business. As such a
few here work a lot of hours and would like to have the
flexibility of working some from home. Yet, I have not
been able to make this happen and have found very little
guidance from any Internet resources.
Here is our network configuration: NT4 (SP6) server which
does it all, including the following: application server
(we run a few acquired and home-grown apps), data server
(we centrally manage - backup - most our data here), e-
mail server (Lotus Domino), Internet server (we all access
our satellite link from here), proxy server (Microsoft's
2.0 - originally this was setup to enable sharing a dial-
up connection to the Internet, yet it is still in place
for security reasons, essentially functioning as our
firewall), DNS (we use static IP addressing internally -
primarily because we could not get DHCP to work
initially), and antivirus server (Norton).
I realize this may seem like a lot for a single NT server,
yet it has served us well - remember we're a small
business - and we've not encountered any performance
problems.
So, my question is what is the simplest, most effective
way to remotely connect to our NT server from a Windows XP
client? And more importantly, in detail, how do we do it -
what are the precise steps? As I alluded to above, I
have tried this via Lotus Notes to simply exchange e-mail
and also tried to access the entire network. Currently,
from my XP client, I get the following error: "676:
remote phone is busy". I have also tried connecting from
my Windows 98 client at home and while I appear to connect
successfully, I'm not able to see or do anything. While
these issues may be easier to resolve, remember I'm
interested in a complete solution - one that will
circumvent any other issues I may run into eventually.
