VPN, Authentication, Browser

[elliotm]

Just had the relevant configurations changed on my managed firewall to allow VPN access.

After dialing up an ISP I then run the VPN software to tunnel through to my firewall. I then connect to an IP address via a browser which then asks me for my username and password. After this I can ping all IP addresses on the our internal network (192.168.100.x - 255.255.255.0). To ping hosts names I added all the server names into the hosts file and can now ping any of the hosts names.

The problem I am having is that I cannot browse the network or map drives to network shares. If I try to connect a share on a server (e.g. \\server1\install or \\192.168.100.9\install) I get the error message or "there are currently no logon servers available to service the logon request". But I can successfully ping all DC's and I can connect to an exchange 2000 server using the name and send and receive email.

If I run a tracert to the IP address the first eight hops fail and then the ninth one is successful to the destination.

I am running W2K with sp3 and trying to connect using w2k pro sp4. The VPN software is NetScreen-Remote - safenet softremote


Any ideas where the problem could be? Firewall, DNS or w2k?? Or am I missing something obvious?

thanks in advance for your help.

 

[Sylvor]

Hiya,

Is your computer a member of the domain at the remote end?

Dave

 

[elliotm]

Tried home PC (Never been on domain) and laptop from work (been on the domain before) but get same results.

 

[Sylvor]

Hmmm,

I had a similar problem with an XP home machine, in the end I simply added it to the domain manually (you cannot join a domain with home edition) and then I set the "workgroup" name to the actual domain. Problem was solved.

I'd ensure that the client PC is a member of the domain and set the domain / workgroup on the client to be the same as the domain you are connecting to.

(Although you must still logon locally to the PC)

D

 

[elliotm]

Sylvor, Thanks for your response. I took the laptop out of the domain and put it a workgroup of the same (domain) name and it worked.

Thanks again