Re: VPN clients can't ping by short name, but can by FQDN

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: J.C. Hornbeck [MSFT] (jchornbe_at_online.microsoft.com)
Date: 03/16/04 

Date: Tue, 16 Mar 2004 15:20:57 -0600

It sounds like you've probably got it setup right. Does an LMHOSTS file
allow it to work? 

-- 
J.C. Hornbeck, MCSE
Microsoft Product Support
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
"Robert T" <rattlingdags@paradise.net.nz> wrote in message
news:moH5c.1701$u%1.259424@news02.tsnz.net...
> Thanks for your reply.
>
> I've set up DHCP to point give WINS info to the clients. The machines that
> are trying to VPN in already belong to the domain (except for my one) so
in
> theory the domains suffixes match. It seems like netBIOS names don't work,
> but DNS do. I thought that DNS would resolve a netBIOS name since they are
> part of the DNS name.
>
> How do I ass the domain suffix? I've set up DHCP with the domain name as
one
> of the scope options, along with the WINS server location and node type
>
> Cheers
>
> Robert
>
>
> "J.C. Hornbeck [MSFT]" <jchornbe@online.microsoft.com> wrote in message
> news:eZQI9s2CEHA.1588@tk2msftngp13.phx.gbl...
> > There shouldn't be anything special to configure to allow NetBIOS name
> > resolution traffic to pass over through the VPN tunnel.  Is WINS running
> in
> > your environment?  Like you mentioned, you probably shouldn't need WINS,
> > especially if the domain suffix's match.  If you don't have WINS then
> > probably the easiest way to resolve this is to add the proper domain
> suffix
> > on the clients, or join them to the domain.  If it were me I'd do that
> > before adding host files.
> >
> > -- 
> > J.C. Hornbeck, MCSE
> > Microsoft Product Support
> >
> > NOTE: Please reply to the newsgroup and not directly to me. This allows
> > others to add to and benefit from these threads and also helps to ensure
a
> > more timely response. Thank you!
> >
> > This posting is provided "AS IS" without warranty either expressed or
> > implied, including, but not limited to, the implied warranties of
> > merchantability or fitness for a particular purpose.
> >
> >
> > "Robert T" <rattlingdags@paradise.net.nz> wrote in message
> > news:pJy5c.1647$u%1.249770@news02.tsnz.net...
> > > Any help would be greatly appreciated!!!
> > >
> > > I have a network with AD on a 2003 Server, and ISA running on a 2000
> box.
> > > I've recently rebuilt the ISA server and replaced the ADSL router.
> > >
> > > VPN clients are now not able to connect to network shares bt short
name.
> > > They can connect by using the FQDN - eg server1.internal.domain.com,
but
> > not
> > > using server1.
> > >
> > > All hosts inside the domain are able to connect no problems.
> > >
> > > RRAS is set to obtain all info from the DHCP server which hasn't
> changed.
> > >
> > > I could get around this by creating entries in the hosts file for each
> vpn
> > > client, but I would like to avoid this if possible.
> > >
> > > Is there a port I need to open for WINs? I would have thought if DNS
was
> > > good, then WINs wouldn't be needed (I haven't needed it yet - all
> clients
> > > are W2K/XP).
> > >
> > > Can anyone help?
> > >
> > > Thnaks
> > >
> > > R
> > >
> > >
> >
> >
>
>

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Need help with naming conflict
    ... > be used before the DNS naming for resolving a computer name? ... > I just not pass down a DNS server to the VPN clients? ...
    (microsoft.public.win2000.dns)
  • Re: Virtual LAN Problem
    ... So I disabled DCHP and put the DNS from the SBS into the allotted ... I re-enabled DCHP and left the SBS DNS address on the device. ... on the clients, they must be getting DNS information from somewhere. ... VPN must use two subnets if the routing is to work. ...
    (microsoft.public.windows.server.sbs)
  • Re: Re: site to site vpn with active directory
    ... >> point all the new clients to this new site and point the dns ... >> data across a vpn how much bandwidth is the replication of AD ... I have set the clients at the remote site to point to the ...
    (microsoft.public.win2000.active_directory)
  • Re: WINS and DNS issue
    ... Do they have their DNS name configured in the SYSTEM CONTROL ... It may be unnecessary to have the server on "both nets" directly. ... things you need to do (AD Domain, DNS clients servers etc.) ... ANd not if the clients register themselves. ...
    (microsoft.public.win2000.dns)