NetBIOS over TCP/IP on RAS dial-up

[Dominik]

I have very big problem I configured RAS routing on dial-
in and WINS server. When I connect to server I can ping
everyone on network but when I try to see other computers
in my network places I canot see anything, and when I try
to use the IP adress to connect to someone I connect to
him but I canot see any of his shares. When I type
IPconfig /all I get all the stuff like it is configured
in DHCP but it always says that DHCP is disabled and
NetBIOS over TCP/IP is disabled, and I tried the solution
from KB292822-wins over ras. The server OS is WIN2000 and
client is WINXP. Please any sugestions are welcome.

 

[Bill Grant]

The things you need to change (outlined in KB 292822) are to prevent
problems with DNS and/or WINS on the LAN, affecting LAN clients.

You don't need Netbios over TCP/IP enabled on the remote client to "see"
machines on the LAN. All you need is for the client to have the correct DNS
setup.

Does the remote client receive the correct DNS address? Does it have the
correct DNS suffix configured in its connection properties (ie the suffix of
your LAN such as mydomain.local)?

If it has the correct DNS server address and the correct suffix it can
ping by name. If ping IPaddress works, ping Computername should also work.
XP should also send your domain credentials to the server to access domain
resources without you needing to change anything.

 

[Guest]

Yes I ve checked all the data and the client gets the
right IP address of the DNS and WINS server but like I
said when I try to connect to RAS server or any other
computer on the network I dont see them in Network Places
and net view or net use doesnt work. When I try to
connect by IP address of the computer I connect to them
but I cant see aither of their shares, and I must use
WINS and not DNS because not all the computers are
registred in DNS and there are some win98 computers.
I tried to reinstall RAS server because before I could
see RAS server in Nettwork places but I couldnt see
anything else and I could connect to computers by IP
address but now even that dont work. So I would be
gratefull on any help.

 

[Bill Grant]

The first thing to do is make sure that browsing is working correctly
on the LAN. Have you set the registry value to prevent Netbios over TCP/IP
on the RRAS interface (as recommended in 292822)? If not, do that then
restart RRAS.

Is browsing working properly on the LAN? No event log errors about
browser elections? Check that there is only one entry for the domain master
browser in WINS. Check again after a remote user connects.

If the LAN clients can browse the LAN, the remote client should be able
to as well, as long as it has the correct WINS address and the correct
domain name. If in doubt, monitor the RAS traffic and see what the client is
sending. It should be sending a name request for <domainname 1B> to get
the IP address of the DMB. When it gets this from WINS, it should be able to
get a browse list.

As far as mapping drives, XP usually sends the correct domain
credentials. (W9x and W2k didn't do it too well). If you have trouble, use
the extra options in NET USE to send your domain username and password.

 

[Dominik]

I tried all the propsed solutions and it didnt work I can
ping everyone on the network but when I try to connecto to
anyone beside on computers with XP it doesnt work it just
says that network path dont exist, it doesnt matter I try
to connect with IP or by DNS name NetBios name or
whatever, but when I try to connect to XP computers I
connect to them but only by IP address. And one other
thing I tried to connect ot that RAS server from Win98
client using netBeui and it works perfectly but on XP I
cant use NetBeui over Dial-up. So if you have any other
ideas I am very grateful?
Thanx

 

[Bill Grant]

If your LAN is running Netbeui it cetainly won't work. Netbeui and Netbt
are independent and do not share browser info. If you are running both you
will have two browsing services running!

I would convert the LAN to use Netbt. Netbeiu is being phased out and is
no longer supported. But if you must, Netbeiu for XP is available on the CD.
See KB 301041.

 

[Dominik]

Well I dont run netbeui I just tried with netbeui on
client for testing purposes but the network is TCP/IP
based with netBT but like I said I can only browse clients
with winXP and only with IP address and not by
computername. So I am with out any ideas?

 

[Bill Grant]

Netbeui on the remote client would do nothing if the LAN clients were not
running Netbeui as well! Netbeui and Netbt do not interact. They build
separate browse lists.

As I said, browsing works if the remote client gets the correct WINS
address, and the browser registers its special netbios browser name with
WINS.

You will just have to debug it step by step. There is no magic
formula.

 

[Dominik]

That means if I have NetBeui on just few computers on LAN
and on the rest I use NetBT, that bowsing will not work at
all, or it will work with clients using Netbeui and not on
the ones using NetBT and reverse???

 

[Bill Grant]

It means that those running Netbeui only will only see other machines
running Netbeui, and machines running Netbt only will only see other Netbt
machines. The two browser services run independently of each other. You will
have two browse lists, one for each protocol. Machines running both
protocols should appear in both browse lists (at the expense of doubling
your network broadcasts).