Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.dcom.vpn    |    VPN protocols, clients, awesomeness    |    2,348 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,236 of 2,348    |
|    News to T. Sean Weintz    |
|    Re: Unable to browse network shares    |
|    30 Sep 04 12:31:45    |
   
   From: a@b.com   
      
   "T. Sean Weintz" wrote in message   
   news:10lm0326sc0s3f3@news.supernews.com...   
   > News wrote:   
   > > Hi   
   > > I am using Checkpoint VPN-1 to connect a few of our home users to the   
   > > company network. They connect either through their local ISP dialup   
   > > connection or an ADSL broadband connection.   
   > > When connected, they are able to ping any IP address within the network   
   > > through the VPN, but are unable to browse any shares.   
   >   
   > That is normal. You won't be able to browse to the shares.   
   >   
   > > \\servername does not work. I get the error "there are currently no   
   logon   
   > > servers available to service the logon request"   
   >   
   > To be expected unless the home machines are in the domain, which they   
   > probably are not.   
      
   They are in the domain - they are laptops.   
      
   >   
   > > net use \\servername gives the error "System error 53 has occurred"   
   > > They can ping server names provided the server is added to the hosts   
   file.   
   > >   
   > > I don't get why they cannot see the network shares.   
   >   
   > two reasons - you can't browse the shares becaiuse yuou won't see the   
   > netbios broadcasts since you are on a different subnet and not part of   
   > the domian and likely the client machines at home also are not set up to   
   > use the company DNS and WINS servers.   
   >   
   > You can't get into the network shares beacuse you are not authenticated   
   > to the servers yet.   
   >   
   > > Is this a "Client for Microsoft Networks" problem? The computer I tested   
   > > this on did not have a firewall.   
   >   
   > No. It's behaving as I would expect from what you describe.   
   >   
   > >   
   > > Any advice as to what may be the problem would be greatly appreciated.   
   > > Thanks   
   > > Alan   
   > >   
   > >   
   >   
   > What happens if you try:   
   >   
   > "net use * \\servername /user:domainname\username"   
   >   
   > That should force it to authenticate correctly - should come back and   
   > ask for a password.   
      
   I get "System error 67 has occurred" which basically means it can't find the   
   network name.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca