Odd VPN name resolution problem. Please...

  • Thread starter Thread starter Lei Hu
  • Start date Start date
L

Lei Hu

Hi there,

There are lots of posts about VPN name resolution problems. And yes, I've
read and tried a lot, but still cannot fix my problem.

I have a small network in my office. The machines are running either Win2k
pro or XP pro (no server installed). The LAN is connected to the Internet
using a Netgear ADSL modem. I use a Win2k pro box as the VPN server to
accept connection from my home box with XP pro. I think I set the machines
and ADSL modem properly. And yes, everything is working perfectly (e.g., I
can ping the server by name, I can use "Net view", and "Net use", etc..)
except that:

(1) The VPN server machine name *doesn't always* appear in "My Network
Places". Probably 9 out of 10 times I cannot see the name. Sometimes, it
does appear, and then some time later, it disappears.

(2) I cannot access *other* boxes in the server side LAN by name. I can ping
them or map network drives using their IP addresses, but just cannot use
their names. As mentioned in point (1), even though sometimes the machines
appear in "My Network Places", I still cannot use them. If I double click an
icon, it says something like the machine is not accessible, but actually it
is.

Yes, I've enabled Netbios over IP option, and I even installed Netbeui, but
it doesn't help.

I sometimes think maybe the VPN server in Win2k pro is not fully functional.

Has anyone got any idea? Please help!

Thanks in advance!!

Lei
 
Lei Hu said:
(1) The VPN server machine name *doesn't always* appear in "My Network
Places". Probably 9 out of 10 times I cannot see the name. Sometimes, it
does appear, and then some time later, it disappears.
Click to expand...

Forget it. You're lucky you get that much. Net'Hood is based on Master
Browser's and Browse Lists. It is not the same as Netbios Naming and Netbios
Naming can work perfectly fine even if Net'Hood doesn't
(2) I cannot access *other* boxes in the server side LAN by name. I can ping
them or map network drives using their IP addresses, but just cannot use
their names. As mentioned in point (1), even though sometimes the machines
Click to expand...
Yes, I've enabled Netbios over IP option, and I even installed Netbeui, but
it doesn't help.
Click to expand...

Get rid of Netbeui, it is irrelevant. It is not "Netbios", it is simply a
protocol that is Netbios compliant.

It requires WINS. You have to run a WINS Server. You can't run WINS without
a Server OS. You can cover for that with a LMHosts file on the client
machine.
 
Hi Phillip,

Thanks a lot for your kind reply.
Forget it. You're lucky you get that much. Net'Hood is based on Master
Browser's and Browse Lists. It is not the same as Netbios Naming and Netbios
Naming can work perfectly fine even if Net'Hood doesn't
Click to expand...

OK, I'll forget it!!
machines

Get rid of Netbeui, it is irrelevant. It is not "Netbios", it is simply a
protocol that is Netbios compliant.

It requires WINS. You have to run a WINS Server. You can't run WINS without
a Server OS. You can cover for that with a LMHosts file on the client
machine.
Click to expand...

I don't have Server OS installed, so WINS is not available. People mentioned
a lot
that if you enable "NETBIOS over IP", naming problems could be fixed. In
theory, I
think that's enough for NETBIOS naming. Looks like it's not true (or maybe
it's true
if you use the server version of VPN?). Yes, I tried the LMHOSTS file, and
it works.
But my problem is that the machines in office use DHCP, so their IPs change.
Phillip, in my situation, besides WINS and LMHOSTS, is there any other way
to
achieve that?

Anyway, like what you said, I'm happy to get this much! Thanks so much!

Lei
 
Lei Hu said:
that if you enable "NETBIOS over IP", naming problems could be fixed. In
theory, I think that's enough for NETBIOS naming.
Click to expand...

In theory it should be enough as long as there is only one subnet. But the
VPN means you have at least two subnets
if you use the server version of VPN?). Yes, I tried the LMHOSTS file, and
it works. But my problem is that the machines in office use DHCP, so
Click to expand...
their IPs change.

Then the LMHosts file is useless.
Phillip, in my situation, besides WINS and LMHOSTS, is there any other way
to achieve that?
Click to expand...

You need WINS. Does the network on the other side of the VPN use WINS? If
it does and the VPN connection is *always* up, then you can add that WINS
Server to the DHCP Settings so they they get this WINS Server from DHCP. As
long as all machine is all the subnet use the same WINS Server everyone is
happy. There could also be multiple WINS Servers as long as they are setup
as "push-pull" partners to each other.
 
Hi Phillip, Thanks a lot!!

Phillip Windell said:
In theory it should be enough as long as there is only one subnet. But the
VPN means you have at least two subnets

their IPs change.

Then the LMHosts file is useless.


You need WINS. Does the network on the other side of the VPN use WINS? If
it does and the VPN connection is *always* up, then you can add that WINS
Server to the DHCP Settings so they they get this WINS Server from DHCP. As
long as all machine is all the subnet use the same WINS Server everyone is
happy. There could also be multiple WINS Servers as long as they are setup
as "push-pull" partners to each other.
Click to expand...
 
Back
Top