Discussion Locked

Unable to browse network when RAS

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

What is the cause of not being able to browse the network after having an authenticated RAS connection.

I'm not sure it is related but since I implemented a CABLE/DSL router for Internet connection sharing of a small LAN I'm experincing the problem. TheRouter is providing DHCP & NAT for the LAN.

5 replies

by rogue7475

Lots of things can go wrong with an RAS connection, so I'll just try and give you some things to check. First, check the session statistics to determine which protocol your RAS session was actually established with. At least you'll be troubleshooting the right protocol. Usually, TCP/IP should be used. Use IPCONFIG or WINIPCFG to get the leased information. Ensure that the subnet mask, DNS servers, and WINS servers are correct. These settings are assigned by the RAS server. Unless of course you have DHCP routing, and then stufff changes :) If you can connect to resources using their IP, i.e. you can ping an IP but not a name, then your DNS settings are incorrect. I hope you found this helpful.

jason

by jacobsen

Thanks for the info. I only have TCP/IP protocol configured for RAS. I configured an IP scope for RAS clients within the DHCP scope of the router. The RAS has WINS running on it. I'm not using DNS on the LAN. I will check my ipconfig to make sure WINS is correct. Also, the RAS client is able to auto create the drive mapping to the RAS server but when I try accessing the mapped drive. I get an error incorrect path.

by william jay

By RAS do you mean dial-up?
Which OS and server? (NT4 with built-in apps)
Which NAT box? (LinkSYS?)

Sounds like the domain name or workgroup name is mis-reported to the remote user.

Error message, please be more specific about the information returned by the error notification, and look in the app and system and security log(s), if any, to help isolate where the problem is really, so we can help to give the solution, for you ...

by jacobsen

Client is running WinMe using Dial-up
4.0 Server running RAS with LinkSYS NAT box.

The log shows Remote user as being authenticated to the domain. But the client is unable to browse the network. I don't recall the exact error message when I tried to access the mapped drive It list the path of the mapped drive and says not found. Thanks for your input. jimj

by william jay

This is not the answer, but we will find it soon. You have the benefit of being there and seeing first hand what is, and I am at a disadvantage for that. Know that communication is the key to all ...
Given: The LAN uses the LinkSys box as a gateway, and for DHCP. An NT4 Server is providing RAS to dialups.
By the way this comment is very contradictory and points to the problems and so to the solutions -> {I only have TCP/IP protocol configured for RAS. I configured an IP scope for RAS clients within the DHCP scope of the router. The RAS has WINS running on it. I'm not using DNS on the LAN.} WINS is not part of tcp-ip, and DNS is required for even simple access to tcp-ip based resources ...
Have you reserved the ip numbers for RAS with the linksys box, and told all the machines to use DHCP for WINS reolution? See, you really have two dhcp servers and possibly two WINS servers running. When they co-respond properly the trouble will go.
Have you searched the server for hosts and lmhosts files, no longer needed or out of date? IF that doesn't straighten it out then let's get physical; I am trying to map this out to understand the layout. Where is the linksys box in relation to the server? (ie: connected to the server on nic2, connected to a hub on an MDX or WAN port, connected to somewhere else ...). OK, now to path not found - You say the RAS client can auto-create the drive mapping to the server but not access the path afterwards. What is auto-create in this context or what procedure is followed? Even in a small network it can take five minutes or more for the shares to be enumerated and distributed, (depending on a few things that are irrelevant at this stage but could prove interesting later as you tune the systems). Also, I have seen where a win3x or win9x machine running Client for MicroSoft Networks needed to make a shared directory and offer it on the network before it could browse i

This discussion is closed to new replies.