Re: DNS a bit odd
- From: "Alex" <nospam@xxxxxxxxx>
- Date: Wed, 18 Oct 2006 15:01:27 +0100
Hmmm, that makes total sense as it's the DNS Suffix that's missing (I can
add it into a manual VPN Connection that I create and everthing works as
expected but I wanted to use CMAK which doesn't give me the option of
including a DNS Suffix).
I've added option 15 into my DHCP server with the string AMT.Internal but
when the client is connecting, it still isn't being allocated the suffix :/
hmmm, might have to figure out how to create a VPN connection without using
CMAK.
"Halcyon" <craig@xxxxxxxxxxxxxxx> wrote in message
news:uCsFEsq8GHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
the NETBIOS resolution you are using to resolve 'bilbo' is a broadcast.
if you configure you dhcp assignment to grant you a default domain name of
AMT.internal, it might allow you to ping on just bilbo and automatically
add the .AMT.internal at the end.
"Alex" <nospam@xxxxxxxxx> wrote in message
news:uwn1uxd8GHA.2248@xxxxxxxxxxxxxxxxxxxxxxx
when connecting to my fairly simple VPN on ISA 2006 server I can only
connect to machines using FQDN rather than just their machine names ...
i.e. internally on my LAN i can 'ping bilbo' but if i connect via the VPN
from outside i have to 'ping bilbo.AMT.internal'
is this normal behaviour, is another protocol allowing me to resolve
bilbo on my internal machines which is not on my VPN machines? How could
I change this so that my VPN machines can access machine names directly
without having to use the full internal entry?
tx
alex
.
- Follow-Ups:
- Re: DNS a bit odd
- From: Alex
- Re: DNS a bit odd
- References:
- DNS a bit odd
- From: Alex
- Re: DNS a bit odd
- From: Halcyon
- DNS a bit odd
- Prev by Date: Re: DNS a bit odd
- Next by Date: Re: DNS a bit odd
- Previous by thread: Re: DNS a bit odd
- Next by thread: Re: DNS a bit odd
- Index(es):
Relevant Pages
|
