Re: After VPN conn. i am not able to ping local comp by NAME

I made some modifications on my client:
- computer identification (domain member, but before that I corrected
primary suffix for vpn connection)
- WINS server
- registry modifications (after my computer was a member of domain i
couldn't ping internal computers - after ping it was returned public ip of
company)

and now:
- after vpn connection and nslookup I get my company gateway
- i can browse my domain and i can browse my home workgroup
- I can ping my internel computers
after ping compname I get compname.domainname and correct internal IP

So everything works fine now BUT ... when i am using my ISP connection is
only for three minutes but it is another subject

MartinN

"Bill Grant" wrote:

> Browsing from a remote client usually doesn't work. As Bob said, a WINS
> server on the LAN is usually required. But that won't necessarily solve the
> problem.
>
> Browsing relies on Netbios names and LAN broadcasts, but LAN broadcasts
> don't cross WAN links. So the remote client doesn't appear in the LAN browse
> list. And the remote site can't see the browse list in your home network.
>
> If you have WINS running on the LAN at work, you should be able to see
> that browse list. It may not work though if the client is on a local LAN (as
> yours is). The problem is the way that a client requests a browse list. It
> will only get the browse list from the VPN server's LAN if it knows the
> Netbios name of that domain.
>
> If a standalone VPN client knows the name of the remote domain, it sends
> a name request to WINS for the special Netbios name <domainname 1b> ,
> which is the domain master browser. If WINS returns the correct IP for this,
> the remote user can get a browse list directly from the DMB.
>
> The browser service was designed a long time ago, long before VPN was
> invented. It can cope with remote sites (because they look just like other
> subnets across a router) but it can't really handle single VPN clients.
>
> MartinN wrote:
> > If I use nslookup comp1 i get::
> > C:\>nslookup comp1
> > Serwer: stefek.mshome.net
> > Address: 192.168.0.1
> > *** stefek.mshome.net can't find comp1: Non-existent domain.
> >
> > else if I use::
> > C:\>nslookup comp1.domainname.pl I get
> > Serwer: stefek.mshome.net
> > Address: 192.168.0.1
> >
> > Nieautorytatywna odpowied«: (non-authorative reply )
> > Nazwa: domainname.pl
> > Address: public IP of VPN server
> > Aliases: comp1.domainname.pl
> >
> > once more my ipconfig:
> > C:\>ipconfig /all
> >
> > Konfiguracja IP systemu Windows
> >
> > Nazwa hosta . . . . . . . . . . . : MARCIN_LAPTOP
> > Sufiks podstawowej domeny DNS . . . . . . :
> > Typ wezla . . . . . . . . . . . . : Mieszany
> > Routing IP wlaczony . . . . . . . : Tak
> > Serwer WINS Proxy wlaczony. . . . : Nie
> > Lista przeszukiwania sufiksów DNS : mshome.net
> > ekokaloria.com.pl
> >
> > Karta Ethernet Polaczenie sieci bezprzewodowej 3: (wireless)
> > Sufiks DNS konkretnego polaczenia : mshome.net
> > Opis . . . . . . . . . . . . . . : 3Com OfficeConnect
> > Wireless 11g PC C
> > ard (3CRWE154G72) #2
> > Adres fizyczny. . . . . . . . . . : 00-0D-54-A2-5B-5D
> > DHCP wlaczone . . . . . . . . . . : Tak
> > Autokonfiguracja wlaczona . . . . : Tak
> > Adres IP. . . . . . . . . . . . . : 192.168.0.191
> > Maska podsieci. . . . . . . . . . : 255.255.255.0
> > Brama domyslna. . . . . . . . . . : 192.168.0.1
> > Serwer DHCP . . . . . . . . . . . : 192.168.0.1
> > Serwery DNS . . . . . . . . . . . : 192.168.0.1
> > Dzierzawa uzyskana. . . . . . . . : 30 pazdziernika 2005
> > 12:28:29 Dzierzawa wygasa. . . . . . . . . : 6 listopada 2005
> > 12:28:29
> >
> > Karta Ethernet Polaczenie lokalne:
> >
> > Stan nosnika . . . . . . . . . . : Nosnik odlaczony
> > Opis . . . . . . . . . . . . . . : Karta PCI Fast Ethernet
> > oparta na Si
> > S 900
> > Adres fizyczny. . . . . . . . . . : 00-00-E2-93-96-67
> >
> > Karta PPP EKOKALORIA:
> >
> > Sufiks DNS konkretnego polaczenia : ekokaloria.com.pl
> > Opis . . . . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> > Adres fizyczny. . . . . . . . . . : 00-53-45-00-00-00
> > DHCP wlaczone . . . . . . . . . . : Nie
> > Adres IP. . . . . . . . . . . . . : 10.10.10.241
> > Maska podsieci. . . . . . . . . . : 255.255.255.255
> > Brama domyslna. . . . . . . . . . :
> > Serwery DNS . . . . . . . . . . . : 10.10.10.1
> > Podstawowy serwer WINS. . . . . . : 10.10.10.101
>
>
>
.

Relevant Pages

  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... Are you saying that an XP Home PC wouldn't be able to connect to a server share over VPN? ... Can ping the SBS but not the client PCs on the same network. ... gateway matches the IP of the remote client, ...
    (microsoft.public.windows.server.sbs)
  • RE: Connection times to devices behind VPN are extremely slow
    ... I understand that the remote VPN client ... You have to rerun the CEICW to make sure your SBS 2003 server have right ...
    (microsoft.public.windows.server.sbs)
  • Re: TS vs VPN
    ... Using TS, w/o VPN ... The remote client connects to your local TS via Remote Desktop. ... "Foo" accesses the SQL server, which is nearby in a protected part of the network. ...
    (microsoft.public.windows.terminal_services)