Windows 2003 Server does not find a Windows XP Professional Computerin a virtual private network

  • Thread starter Thread starter Dirk Lehmann
  • Start date Start date
D

Dirk Lehmann

Hello,

I have two locations which are connected with two routers over the
internet. There is a vpn channel configured between the routers. The
configuration of vpn tunnel between is successfull and working.

Now my Windows 2003 server at the one location is connected with a
Windows XP Pro client at the other location.

The routers are configured to accept NetBIOS-Dataflow over the
IPSec-tunnel. With other words: On the routers the NetBIOS-Dataflow in
the IPSec-tunnel is enabled.

I am able to ping all routers and all clients in the two network segments.

But the situation is: Im not able to find the windows xp pro client (I
was searching for the computername and the ip-adress) or the workgroup
of the windows xp pro client (MSHOMENETWORK)in the network enviroment.

Please tell me what should i configure, that both computers will find
each other in the network enviroment.

Thank you.

Regards,

Dirk Lehmann
 
The problem doesn't lie in the ability to move netbios traffic across the
tunnel, but in the fact that NetBIOS (the browser) is broadcast based. Since
the two locations have different subnets, the broadcast addresses are
different. You can manually make an lmhosts entry if it's just for one
computer at each end. Or you can set up WINS on the Server. Sometimes it's
easier to just create a desktop shortcut to the UNC path using the IP
address, i.e. \\192.168.100.22.

...kurt
 
Kurt said:
The problem doesn't lie in the ability to move netbios traffic across the
tunnel, but in the fact that NetBIOS (the browser) is broadcast based. Since
the two locations have different subnets, the broadcast addresses are
different. You can manually make an lmhosts entry if it's just for one
computer at each end. Or you can set up WINS on the Server. Sometimes it's
easier to just create a desktop shortcut to the UNC path using the IP
address, i.e. \\192.168.100.22.

..kurt
Click to expand...

Hello Kurt,

today I write you that I yust changed to the windows 2003 server (I
market the partition as a boot-partition) and I tried to create a
shortcut to \\192.168.2.2

Result: It was not possible to create a shortcut.

I also checked LMHOSTS.SAM and there is a entry for like this:

192.168.2.2 HP56852474523

I am able to ping the 192.168.2.2 from the windows 2003 server
(192.168.1.33) after some tries.

I want to access to the network shares on 192.168.2.2.

Please help me accessing this network shares. Thank you.

regards,

Dirk Lehmann
 
Back
Top