On Fri, 27 Dec 2002 07:55:12 +0000, the artist formerly known as Mike
proclaimed:
Quote:> BW -- I was referring to an earlier VPN post in this NG
> to which you had responeded. Your memory is intact, I
> hadn't posted on this topic myself previously.
Ok, I don't even remember said post. My memory is going. I was going to
do some mental retraining exercises using my tablet pc to keep it fresh,
but Terri can't get me one!
Quote:> I'm not trying to have both internal network and Internet
> access at the same time. That works fine from the
> office, except for proxy and filter delays ;)
OK, I am not familiar with the particular VPN software you are using, but
if you provide a link, I would be happy to do some research for you and
see what I can find so I may be able to help better. So, I'll try to help
generally for now:
The first thing you
need to do is connect to your VPN. Then post what the output of ipconfig
/all is, particularly your entries for the DNS servers.
Quote:> What I'm trying to do is connect to the office via VPN
> using all the same stuff (clients, configurations, etc)
> as we use for all other remote users (ie a reasonably
> robust suite). But for some reason only this tablet
> fails to connect properly. The VPN client makes its
> connection fine, but the email client only sees its host
> if I use the numeric IP instead of the name.
Which is definitely a DNS issue, we just have to isolate it a little bit
better to get you a resolution (hopefully).
Quote:> Unfortunately this leaves out the corporate address book
> which is kinda necessary for a lot of my email and is not
> changeable in the client configuration. I did implement
> the "fix" Charlie suggested for my calendar client, and
> it worked fine, so I'm trying to track down the other
> hosts info. Still don't know how I'll resolve the
> network drive (lack of) access issues.
Well, depends on how many network drives you are trying to connect to. If
it is only a handful, then the quick and dirty way is to chuck em in your
hosts file. I am not on a windows box at the monent, but it is in
\%windir%\system32\drivers\etc\hosts I belive. If you need to connect G:
to \\server1\Mikes_share then just a put an entry in your hosts file
similar to this once you know it's ip address:
ip.address.of.server servers.full.name server
example:
10.10.5.2 server1.corporate.com server1
The syntax may be slightly different, just follow the examples in the
comments section at the top of the file.
There is also an lmhosts file where you should put a similar entry
following the convention there. (don't know enough specifics about your
network to be sure, but having it in both files isn't harmful).
Quote:> All this would be much easier if the IT group wanted to
> cooperate. But I've bought an "unsupported device"
> (Tablet PC) and I'm working with the dreaded and hated
> Microsoft product line. Thus, I'm on my own. When will
> this holy war end?
Well, some IT groups are tarts. And others get turned into tarts by being
overburdened and understaffed by management. I take it you installed the
VPN client yourself, then? They may have a customized version with
specific configurations that they install, that you may not have on yours.
Quote:> So, I'll try your other suggestions as well. None-the-
> less, I'm mystified as to why these issues arise only on
> this device, makes me suspect an XP "feature" or Tablet
> issue as all other variables have remained constant.
It is hard to say without more information. If the VPN client wasn't
installed from the same location on each machine, there may be differences
in them that are unrelated to the tablet, per se. It could also be some
quirkiness on the tablet that I am unaware of as you say - perhaps a
conflict between your VPN software and the tablet PC's extras.
A good place to take a peek is in your eventviewer and see if there are
any conflicts, but I suspect the VPN software is working ok, it just isn't
populating the internal DNS servers to your machine properly.
--
One OS to rule them all, One Passport to find them,
DRM to bring them all and with the EULA bind them.