Re: Solution for invisible network shares when VPN into SBS2003?

From: Wes (wes.kjc_at_online.ntlworld.com)
Date: 11/05/04


Date: Fri, 5 Nov 2004 21:55:19 -0000

Hi Stefan,

The Hosts file is used for FQDN resolution (\\hostname.domain.local) and the
LMHOSTS file is for NetBIOS name resolution (\\servername).

The files are only needed on the client side to help your client find your
server. If you are able to connect to the shares every by using
\\ipaddress\sharename but not by using a NetBIOS or FQDN then your problem
can only be with name resolution.

Kind regards,

Wes

"Stefan Graf" <stefan@elotec.at> wrote in message
news:ON$J7NxwEHA.3528@tk2msftngp13.phx.gbl...
> Hi Wes,
>
> Hmm, yup it works with the IP adress...
>
> When using ping hostname.domain.local the Hostnames are resolved, so why I
> have to bother with LMHOSTS+Co? I thought that is WinXX stuff...
>
> However, do I have to configure Hostfiles an the server, client or both?
>
> Thank you!
>
>
>
> "Wes" <wes.kjc@online.ntlworld.com> schrieb im Newsbeitrag
> news:ODgKtPqwEHA.2908@tk2msftngp13.phx.gbl...
>> Hi Stefan,
>>
>> Are you able to connect to the server using \\IPAddress and get a list of
>> shares. If so, you may wish to add entries to your HOSTS and LMHOSTS
>> files to allow your computer to resolve the FQDN or servername.
>>
>> Kind regards,
>>
>> Wes
>>
>> "Stefan Graf" <stefan@elotec.at> wrote in message
>> news:uMcUAJqwEHA.3844@TK2MSFTNGP12.phx.gbl...
>>>I also have this problem with network shares when trying to connect via
>>>VPN:
>>>
>>> After establishing a VPN connection I can not connect to shared folders
>>> on the server. It responds to pings, also running clients respond to a
>>> ping.
>>> All I see when connecting to the server like \\servername is my own user
>>> folder.
>>>
>>> Spent hours looking for a solution, maybe someone has it?
>>>
>>
>>
>
>



Relevant Pages

  • Re: exim HELO=fully qualified host name?
    ... > The argument field contains the fully-qualified domain name of the ... > If the client gives a domain name that is not fully-qualified, ... I was talking more about the resolution of the FQDN (when the client ... and refusing my messages just because the server ...
    (Debian-User)
  • Re: exim HELO=fully qualified host name?
    ... |> client system does not have a meaningful domain name, ... | gives a valid FQDN). ... and refusing my messages just because the server ... Find a different provider. ...
    (Debian-User)
  • RE: Remote DNS Issue
    ... When a client in Office C runs the nslookup command, ... Server: dnsr1.sbc.global.net ... So she IS able to disjoin and rejoin the domain... ... is FQDN,A FQDN is a complete DNS name,Fully qualified domain name. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN routing - single NIC
    ... can, routing is working, so adding static routes won't change anything. ... need to look at name resolution. ... check that the client ... This is a single NIC w2k3sp1 server. ...
    (microsoft.public.windows.server.networking)
  • Re: exim HELO=fully qualified host name?
    ... the FQDN and the IP address seen by the server won't ... I think requiring the name to resolve ... > to the same address as the client connecting is being too strict. ... I think that requiring a FQDN is even ...
    (Debian-User)

Loading