[Newbie] Problem whit vpn&router ip config

[c3k]

I'm trying to install a vpn between two pc connect to internet whit ADSL. In both pc is installed win200pro. One of the two machine is on a lan connected whit a router and i use it as client (i thing is the simplest metod). When I try to connect i recive some errors:
1.It connect whitout error but when I browse the LAN I can't see the remote pc.
2.When I ask for the same ip i have on the lan i recive error 52: Name duplicated and it don't connect.

If can help this is the netstat:

- Scheda Ethernet Connessione alla rete locale (LAN):

Suffisso DNS specifico connessione:
Indirizzo IP. . . . . . . . . . . : 192.168.1.40
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . : 192.168.1.1

- Scheda PPP Connessione privata virtuale:

Suffisso DNS specifico connessione:
Indirizzo IP. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Gateway predefinito . . . . . . . :

The server of the VPN take ip 192.168.1.1 (I've configure it to give from 192.168.1.0 to 192.168.1.255).

How can I make it works??? Someone can tell me where can I find a tutorial or something simple that can help me?

 

[John Lewis]

For starters, you need to change some of you addresses for this to work. Start with my rather lengthy post dated Jan 15 in thread463-447092.

Additionally, you can never have the same ip address assigned to two network devices, even if they are on the same computer. The VPN is a separate network device even though it does not have a separate physical device.

Read the other thread and post back if you have questions or problems.

 

[c3k]

Thanks for your tips. I've change my addresses now the local lan is on 192.168.1.x and the vpn server give addres from 192.168.2.0 to 192.168.2.255. When I'm connect I've 192.168.1.40 local address and 192.168.2.40 in the vpn (server has 192.168.2.1) but i still can't see the remote computer in the network resouces...
Can you tell me something about DNS and WINS page in virtualprivate network->proprieties->Network->TCP/IP->proprieties->adwanced ?

 

[John Lewis]

Well, your on the right track with DNS/WINS. You use a DNS server to translate url's (

http://www.tek-tips.com)

to ip addresses (xxx.xxx.xxx.xxx) This requires a DNS server, in that case provided by your ISP.

WINS does a similar job, but for netbios names instead of url's. A WINS server would be great, but I am working with the assumption that you do not have a server that is capable of acting as a WINS server. Generally requires W2K or NT server (not workstation or professional).

There is a way around this problem. On the page that has the DNS and WINS server setup, check the box for 'Enable LMHOSTS lookup'. Next you will need to create an 'lmhosts' file. Search your computer for a file named 'lmhosts.sam'. When you find it, right click on it and select 'Open containing folder'. Right click on a blank spot in the folder and select New --> text document. Type 'lmhosts' for the name of the file. No period, no extension, just 'lmhosts'.

Open the new file with your favorite text editor . . I like notepad as well as anything. If all is good, you should have a blank file. You need to add one line for each computer you are trying to access, including your own. Each line should look like this:

xxx.xxx.xxx.xxx ComputerName #PRE

Replace the xxx.xxx.xxx.xxx with the ip address for the computer (remeber to use the VPN address, not the regular address), the ComputerName with the name you entered in network configuration, type the #PRE exactly as is, no space and in caps. Make sure you place a blank line at the end of the file. Save the file, make sure that the name stays 'lmhosts' -- some editors insist on putting .txt at the end.

Make sure that your username/password exists on each machine and that the workgroup name is the same on each machine. Also make sure that you have at least one resource shared on each computer.

Reboot the machine, start the VPN and try again.

If it doesn't work, a few things to check.

In a command window, type 'nbtstat -c' . That should return a list of the computers in the lmhosts file. Each one should be listed three times. If you don't get the list, most likely the name of the file is not correct, or the file is in the wrong folder.

If the nbtstat output looks ok but you still can't connect, in a command window type 'ping xxx.xxx.xxx.xxx' replacing the xxx.xxx.xxx.xxx with the VPN address of the other computer. If that doesn't work, ping the VPN address of the computer that you are working on. When you report your results, report the exact message that you get from the ping -- request timed out, unknown host, no route to host, etc.

If everything looks good to this point and you still can't get Network Neighborhood to work, complete each of the following and report your results:

In a command window, type 'net view'. That should return a list of computers that are accessible. Similar to opening Network Neighborhood, but with less overhead.

In a command window, type 'net view \\ComputerName'. Subtitute the name of the remote computer with ComputerName. Repeat with the name of the local computer. You should get a list of shared resources. If you don't get a list, report the error and try 'net view \\xxx.xxx.xxx.xxx' replacing the x's with the remote and local ip addresses.

That should give you a good start. Report back any problems.

Good luck!

 

[c3k]

nothing is changed... I can connect whit ip but not whit computer name and the computer still not appears in Network Neighborhood...
I make the change to lmhosts on my machine only (the client on the VPN). I must make it on the server too? In the DNS tab there are some options did i select/deselect/change something?

here my results (something in italian...sorry):
lmhosts file:

192.168.2.1 futsrl #PRE


C:\>nbtstat -c

Connessione alla rete locale (LAN):
Indirizzo IP nodo: [192.168.1.60] ID ambito: []

Tabella nomi cache remota NetBIOS

Nome Tipo Indirizzo host Durata [sec]
-------------------------------------------------------------------
FUTSRL <03> UNIQUE 192.168.2.1 -1
FUTSRL <00> UNIQUE 192.168.2.1 -1
FUTSRL <20> UNIQUE 192.168.2.1 -1

\Device\NetBT_Tcpip_{42ACD804-6604-4275-8D1B-A084C1F77EBE}:
Indirizzo IP nodo: [192.168.2.60] ID ambito: []

Nessun nome nella cache

C:\>ping 192.168.2.1

Esecuzione di Ping 192.168.2.1 con 32 byte di dati:

Risposta da 192.168.2.1: byte=32 durata=93ms TTL=128
Risposta da 192.168.2.1: byte=32 durata=94ms TTL=128
Risposta da 192.168.2.1: byte=32 durata=94ms TTL=128
Risposta da 192.168.2.1: byte=32 durata=94ms TTL=128

Statistiche Ping per 192.168.2.1:
Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 93ms, Massimo = 94ms, Medio = 93ms

C:\>ping 192.168.2.60

Esecuzione di Ping 192.168.2.60 con 32 byte di dati:

Risposta da 192.168.2.60: byte=32 durata<10ms TTL=128
Risposta da 192.168.2.60: byte=32 durata<10ms TTL=128
Risposta da 192.168.2.60: byte=32 durata<10ms TTL=128
Risposta da 192.168.2.60: byte=32 durata<10ms TTL=128

Statistiche Ping per 192.168.2.60:
Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 0ms, Massimo = 0ms, Medio = 0ms

C:\>net view
Nome server Note

-------------------------------------------------------------------------------
\\DEGCAD
\\DEGCAD2
\\DEGELE
\\DEGVIDEO
\\FLCAD
\\SERVER
Esecuzione comando riuscita.


C:\>net view \\futsrl
Errore di sistema 53.

Impossibile trovare il percorso di rete.


C:\>net view \\192.168.2.1
Risorse condivise su \\192.168.2.1



Nome cond. Tipo Lettera Commento

-------------------------------------------------------------------------------
C Disco
D Disco
E Disco
hppsc220 Stampa hp psc 2200 series
Esecuzione comando riuscita.

 

[John Lewis]

Sorry for the delay. Lost the thread for a bit.

lmhosts looks fine, nbtstat -c looks good. Couple of possible issues. The workgroup name of your computer needs to be the same as the workgroup of the server. Don't think that is the problem here, as you should be able to 'net view COMPUTERNAME' anyway, maybe just not see it in network neighborhood. The more critical issue, the computer name in your lmhosts file has to match the computer name as entered on the server.

Try 'ping computername' instead of ping by address. Report results.

Also, check to make sure that 'file & printer sharing for MS networks' is installed on the VPN connection as well as the local area connection. If it is missing on one or the other, or if it is disabled, correct that and try 'nbtstat -c' again. I expected to see stats for two adapters there. Which adapter has the 192.168.1.60 address?

 

[John Lewis]

Sorry for the delay. Lost the thread for a bit.

lmhosts looks fine, nbtstat -c looks good. Couple of possible issues. The workgroup name of your computer needs to be the same as the workgroup of the server. Don't think that is the problem here, as you should be able to 'net view COMPUTERNAME' anyway, maybe just not see it in network neighborhood. The more critical issue, the computer name in your lmhosts file has to match the computer name as entered on the server.

Try 'ping computername' instead of ping by address. Report results.

Also, check to make sure that 'file & printer sharing for MS networks' is installed on the VPN connection as well as the local area connection. If it is missing on one or the other, or if it is disabled, correct that and try 'nbtstat -c' again. I expected to see stats for two adapters there.