Re: Remote desktop over a VPN

Hi Crane,
Thank you for your information.
In fact, the real problem is that even if the Ipsec VPN tunnel is made
between networks, from SBS LAN client computer I can always ping to any
client in the remote network, but just "sometimes" I can remote desktop
to them: I effectivily could remote desktop several times, but almost
always I get a "Remote desktop desconected" error after a while.
This said, I'll give you the information you asked:
1 - LAN (all Windows XP pro) - SBS 2003 SP1 - Cable modem
----Internet---- Linksys WRV54G - Remote network (all Windows XP pro)
2 - The following is the result oh Ipconfig /all on the SBS server:
Configuración IP de Windows



Nombre del host . . . . . . . : rosario

Sufijo DNS principal . . . . : telequal.local

Tipo de nodo. . . . . . . . . : desconocido

Enrutamiento IP habilitado. . : Sí

Proxy de WINS habilitado. . . : Sí

Lista de búsqueda sufijo DNS : telequal.local



Adaptador Ethernet Conexión de área local del servidor:



Sufijo conexión específica DNS:

Descripción . . . . . . . . . : Intel(R) PRO/100+ Management
Adapter

Dirección física. . . . . . . : 00-02-B3-19-F6-46

DHCP habilitado . . . . . . . : No

Dirección IP. . . . . . . . . : 10.0.0.2

Máscara de subred . . . . . . : 255.255.255.0

Puerta de enlace predet.. . . :

Servidores DNS. . . . . . . . : 10.0.0.2

Servidor WINS principal . . . : 10.0.0.2



Adaptador Ethernet Fibertel:



Sufijo conexión específica DNS:

Descripción . . . . . . . . . : NIC Fast Ethernet PCI Familia
RTL8139 de Realtek

Dirección física. . . . . . . : 00-C0-DF-08-B4-78

DHCP habilitado . . . . . . . : No

Autoconfiguración habilitada : No

Dirección IP. . . . . . . . . : XXX.XXX.XXX.YYY

Máscara de subred . . . . . . : 255.255.255.0

Puerta de enlace predet.. . . : XXX.XXX.XXX.1

Servidor DHCP . . . . . . . . : ZZZ.zZZ.ZZZ.ZZZ

Servidores DNS. . . . . . . . : 10.0.0.2

NetBios sobre TCPIP . . . . . : Deshabilitado

Concesión obtenida. . . . . . : Martes, 22 de Noviembre de 2005
03:19:16 p.m.

Concesión expira. . . . . . . : Martes, 22 de Noviembre de 2005
09:19:16 p.m.

The following the ipconfig /all from the lan client where I'm working
now and trying to remote desktop:
Configuration IP de Windows



Nom de l'hôte . . . . . . . . . . : Odisea

Suffixe DNS principal . . . . . . : telequal.local

Type de n?ud . . . . . . . . . . : Hybride

Routage IP activé . . . . . . . . : Non

Proxy WINS activé . . . . . . . . : Non

Liste de recherche du suffixe DNS : telequal.local

telequal.local



Carte Ethernet Connexion au réseau local:



Suffixe DNS propre à la connexion : telequal.local

Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Controller

Adresse physique . . . . . . . . .: 00-12-3F-DB-98-69

DHCP activé. . . . . . . . . . . : Oui

Configuration automatique activée . . . . : Oui

Adresse IP. . . . . . . . . . . . : 10.0.0.11

Masque de sous-réseau . . . . . . : 255.255.255.0

Passerelle par défaut . . . . . . : 10.0.0.2

Serveur DHCP. . . . . . . . . . . : 10.0.0.2

Serveurs DNS . . . . . . . . . . : 10.0.0.2

Serveur WINS principal. . . . . . : 10.0.0.2

Bail obtenu . . . . . . . . . . . : Martes, 22 de Noviembre de
2005 05:29:00 p.m.

Bail expirant . . . . . . . . . . : Miércoles, 30 de
Noviembre de 2005 05:29:00 p.m.

And the following is the ipconfig /all from a remote client (15' ago, I
got the "Remote desktop desconected" error, now I could remote
desktop!!! WHY!!!):


Configuration IP de Windows



Nom de l'hôte . . . . . . . . . . : dao-cb

Suffixe DNS principal . . . . . . :

Type de n?ud . . . . . . . . . . : Inconnu

Routage IP activé . . . . . . . . : Non

Proxy WINS activé . . . . . . . . : Non

Liste de recherche du suffixe DNS : linksys



Carte Ethernet Connexion au réseau local 2:



Suffixe DNS propre à la connexion : linksys

Description . . . . . . . . . . . : Intel(R) PRO/1000 MTW
Network Connection #2

Adresse physique . . . . . . . . .: 00-0D-56-07-0B-DD

DHCP activé. . . . . . . . . . . : Oui

Configuration automatique activée . . . . : Oui

Adresse IP. . . . . . . . . . . . : 192.168.16.103

Masque de sous-réseau . . . . . . : 255.255.255.0

Passerelle par défaut . . . . . . : 192.168.16.1

Serveur DHCP. . . . . . . . . . . : 192.168.16.1

Serveurs DNS . . . . . . . . . . : 192.168.16.1

Bail obtenu . . . . . . . . . . . : mardi 22 novembre 2005
20:39:36

Bail expirant . . . . . . . . . . : mercredi 23 novembre 2005
20:39:36

Finally, in ISA 2004 for all this to work, I created the VPN Remote
network using Ipsec (the only possibility given by the Linksys router
in the remote network?), and the correspondig network rule and firewall
rule. This seems to work nice, since I can always ping the remote
clients (and the status of the Linksys router says also "connected"

If you have some suggestions, I'll be looking for them.

Thank you again!

Omar

.

Relevant Pages

  • Re: ASP.NET -> SQL Server : Impersonation not working!
    ... when we use implicit impersonation like: ... session which doesn't have network credential for further network hop. ... the asp.net use clientside credential to access the remote sqlserver will ... browser, when the IIS accept the clientside credential, it ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VPN on Small Business Server 2k3
    ... IP address of the internal nic on the SBS box? ... XP client that is trying to connect? ... but could not browse the network. ... > The remote client is connecting from an outside site. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop asks for Terminal Server to validate user/password
    ... My laptop is running WinXPPro and is member of the same TomNet ... In a remote desktop newsgroup - this is starting out badly. ... My home network is not accessible for the Big Bad World. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: RDP & IP security help
    ... plenty of reading to do this weekend. ... Client administration: how will you configure and administer the clients? ... Network protection: how will you protect the network from a dangerous ... >> You need something to provide secure remote access. ...
    (microsoft.public.windows.server.security)
  • RE: Remote Desktop/Term. Serv information leakage
    ... How about creating a VPN tunnel to the "isolated" network and connecting ... Subject: Remote Desktop/Term. ... This has nothing to do with Remote Desktop being "possible to configure ... "Remote Admin" was admin user only, ...
    (Pen-Test)