Kurt,
Thanks for the help, but we have a problem: My 48 years as a
programmer/analyst on mainframes didn't prepare me for all the
communications whiz-bang jargon I'm surrounded with today. Let me give you
some more information so that you will understand my situation, and maybe be
more elementary with your help.
We use Win95 because we're using a general ledger system I wrote in various
BASICs (M, GW, Q) 25 years ago under DOS. It's still running fine, and my
cut of the profits earns me an extra $500 or so each year. When we tried to
move to Win98, we had trouble with printing (I don't remember the details),
and so we just stayed with Win95 and DOS.
The office has a server with three clients hooked directly to it, and two
available by dialup (me and the boss's daughter). We're not sure just why
we set up the server -- it's not being used effectively -- but it's there,
doing a payroll service for a bunch of customers. It's almost an
hour's drive from my house, so with gas at $3.00 a gallon, I do most of my
support via telephone. Ordinarily, I use pcAnywhere, but it's not installed
on the server (yet) so I thought I would dialup the server to transfer a
file I wanted to work with. That brings you up to date with the whys and
wherefores.
Now, for why you'll have trouble talking to me: I don't grok "VPN", "routed
connection", "ping", and "UBC path".
You ask "Can you connect using...". I find this confusing. Right now, I'm
trying with the WinXP system. I do connect, as far as I know. When I look
at "Network Connections" I can see the network I'm using and its status is
"connected", so your question doesn't seem to fit. The problem is that the
server doesn't appear under Windows Explorer. In one of my posts, I
mentioned that the problem didn't occur (i.e., I could see and access the
server in Windows Explorer) using the Win95 system. I would like for the
problem to disappear permanently.
I hope you had a happy Fourth!
Bud