Browsing network shares over RAS

[captdef]

First, to give you some background on the network setup:

- Windows 2000/NT server heterogenous, single domain structure network. Name resolution through WINS.

-Workstations/Laptops connecting to network locally and through RAS are Windows 2000.

-PDC is a Windows 2000 server and so is the file server I'm having a problem with.

So here's the problem. We have shares set up on a file server that work perfectly fine when one of our workstations is connected to the LAN, however when dialing in through RAS the same workstation is unable to see any shares on said server. The server is pingable by name and shares on other servers on the network work just fine. I can do a nbtstat on the problem server successfully, but no available shares are seen trying a net view. I've even opened up shares on other LAN connected workstations through the RAS connection without issue.

The laptops/workstations are set up to log on with cached credentials when they are disconnected from the LAN, so it's the domain authentication as usual using a locally cached profile (we use roaming profiles). We are not having users log on to the laptops using dial-up networking (the checkbox option at login) as the login scripts we normally run for LAN connected workstations are excruciatingly slow over dial-up. To connect to our network through RAS we have setup dial-up sessions that use their login credentials for authentication.

Like I said, every other share on our network seems to work without a hitch through RAS except those located on one particular file server.

Any ideas would be greatly appreciated.


~TK

 

[Guest_imported]

so what happens after you dial in and you then go to start |run | \\servername ? We have to then log in as domain\username and pw.

after we dial in thru ras, that's how we get at our network shares but it is way slow. bg

 

[Guest_imported]

pardon me, what we actually do after dialing in and authenticating via ras, is go to

start | run | then type in ip of the server not the name (seems to speed things up, relatively), then we are prompted w/ a log in that you have to submit domain\username and then pw. still way slow.

 

[captdef]

\\servername requests to any share on that server give a Network path not found error. Like I said, only to one particular server's shares. All other servers work just fine and don't prompt for username and password. Which they shouldn't considering applicable credentials were already passed to the servers during login.

Attempting to map a drive has the same effect, even when attempting to map the share point using domain admin credentials.


-TK