General discussion

Locked

Remote and Can't Browse

By bex ·
Intention: To setup RAS so 6 users can connect to the network and browse resources.
Actions so far: We have;
Installed RAS on a standalone server which is also the Exchange Server. This standalone also has WINS installed.
Configured the client (Windows ME laptop) with the domain name in the workgroup field on the ID tab of Network Neighbourhood properties.
Used TCP/IP as the only dial up protocol.
Brought down the firewall and tried to sort out the problem.
Given full permissions to the connecting username.
We have applied Service Pack 6a.
We have also tried dialing in from an NT server and not got any results.
What we can do:
Ping the PDC from the standalone, ping the client from the PDC. A ping from the client to the PDC produces only one response out of 4. Connect to the RAS server from the client and get authenticated
Can see all configured workstations and domain controllers in the WINS database. We have Unix and Netware boxes on the network as well.
THE PROBLEM: We cannot browse the network. When we try we get the message;
"Unable to browse the network. Windows is unable to gain access to the network. This may be for a number of reasons"
WHO'S THE BRAINHEAD WHO CAN SORT THIS OUT FOR ME!!!!!!!!!!

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Remote and Can't Browse

by rddove In reply to Remote and Can't Browse

I can suggest a workaround for your problem. Edit your HOSTS file on the laptop and add the hostname and ip address of the server. You can then do a search for the PC when you are dialed in and it should find it. Create a shortcut to the desktop.

Collapse -

Remote and Can't Browse

by bex In reply to Remote and Can't Browse

The question was auto-closed by TechRepublic

Collapse -

Remote and Can't Browse

by Stillatit In reply to Remote and Can't Browse

To browse you will need netbui protocol, with the option checked for netbui over tcp/ip.

Next, the user needs to be able to find a PDC or BDC.

In the user's LMHOSTS file, make an entry for the BDC or PDC, and incldue both the #PRE and #DOM tags. LMHOSTS is in the Windows directory for Win95 and in Winnt\system32\drivers\etc for NT. It does not exist by default, but there is a file LMHOSTS.SAM created by default which includes instructions and examples. The example line for this case is:
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
Note that the initial # designates a comment. Remove it, change the IP, change the system name, and change the domain name. Then save the file with the name "LMHOSTS." (with no extension) in the same directory.

Collapse -

Remote and Can't Browse

by bex In reply to Remote and Can't Browse

The question was auto-closed by TechRepublic

Collapse -

Remote and Can't Browse

by bex In reply to Remote and Can't Browse

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums