"Lanwench [MVP - Exchange]"
Randy Shearer wrote:
Then why do you need to browse?
Although I can resolve to the computer name, I can see it's computer name.
In a command window I can ping by the name or the IP, but if I "net view" I
get an error 53. Same for net use, of course. So that is why I need to
browse.
Meaning, if you have everything you need to access in your lmhosts file, is
browsing across the VPN connection really necessary? You don't need to
browse just to access something, presuming you can resolve the name via
LMHOSTS (and have the #DOM, #PRE, 0x1b setup properly in there)
Can't you just go to \\server\share?
or even \\server ?
I can ping to \\server, wich is just name resolution from the lmhosts... to
browse to \\server\share is to really browse, and that does not work. So,
no mapping will work. Error 53.
Do you need to browse to, use, objects that don't have static IP addresses
on the remote network?
Everything I need to map to has a static IP. It is just a few servers.
Did it register in the WINS database? Is *everyone* registering in the WINS
database?
I don't know how to check that, being remote from the wins server. But when
at the office, I recall looking at the wins database (maybe a year ago, and
it had everybody on the LAN. We didn't have any remotes back then.
I probably didn't phrase that very well. I'd disable the use of the LMHOSTS
file when trying to use WINS to test - and make sure you're getting the info
from WINS.
Allow you to browse objects on the remote network - which LMHOSTS doesn't
really do.
Not quite - WINS is dynamic, so clients register to it, regardless of IP
address. If your computer, and all the computers you want to browse, are
registered in the WINS database, you can browse and see them. LMHOSTS won't
do that; entries in it are static. It doesn't let you browse - it just maps
NetBIOS names to IP addresses.
It resolves NetBIOS names - and once you've got that, and can see the
object, you can see the shares on it by browsing.
ok - but Wins won't help with browsing past/inot the pc name will it? If
so, then Wins would have a listing of each pc's shared resources? I didn't
think Wins did that. ??? Does Wins not just get you to the IP address,
and then your direct communication using NetBIOS lets you query the machine
for it's shared resources? I don't want to say your wrong, as I am very
eager to learn, and you're likely right... in fact I hope you are.
I
am simply stating the way I thought is was. I will try a Wins setup
again... more carefully this time ;o)
If you can get it working so you can browse, you can see the objects & any
shares defined on them.
?
Do you see a 1b entry for your domain? 1c?
Yes, I see the 1C for the PDC address, and the 03, 00, 20.
oh, why that is kinda personal don't you think? ... but I think I am
looking ok today.
Ohhhhh...
you mean how am I looking at the machine...
sorry, I am
getting silly now.
I was using "net view" to try and see the shares.
no, the DSL gives my PC a valid internet address, on the PC's PPP interface,
so no nat.
there is a firewall, and I will try to disable it for my next wins test...
but in my trials to date it has not made a difference.
I have just created open ports when needed. I've been getting the same
results with or without the firewall enabled. I did in fact spend two days
on this with no firewall installed at all. I thought it best to remove it
totally to be sure it was not the problem.
In any case, you have me wondering about getting Wins working.. so I will
take the firewall out when I try Wins again.
Firewall anywhere in use?
Are you sure your DSL modem isn't doing NAT as well?
Is the router on the remote network doing NAT? I'd presume it is.
I'm not sure whether this is the problem, but it may be related.
NAT at the other end should not be a problem, should it?
That's not what it does. Think of it like a DNS database you can do lookups
to, but for NetBIOS names.
No.
hmmm.. ok. I can see that I'll be having some homework after this is all
said and done.
Again, I can't say. It could be the router on the other side? I don't use
PPTP - I use IPSEC VPN through a firewall & a proprietary client, and with
AD on the remote network, usually just have the remote user specify the AD
DNS server for resolution, so I'm not quite sure. Browsing over VPN
connections can be very difficult.
I believe the firewall client I have here (software), from Netscreen, is
using IPSec. I am connecting to a Netscreen appliance at the office. The
VPN seems to setup fine. I can do anything I wan't to an XP machine at the
office (browsing, mapping, rights, etc...). It is only the NT servers I
cannot see properly. My understanding is that XP will use Dynamic DNS to
resolve other network machines that also support Dynamic DNS... but NT not
supporting this, it must use "NetBIOS over IP" to accomplish the same. (at
least that is what I have read over the past week.)
