I ran into a behaviour that goes beyond my understanging and I’d be glad if someone could bring some light into this matter…
We’re using VPN to connect remotely to the office network from home and that works with no problem. Once connected the remote desktop also works beautifully. It’s the network shares that are giving the hard time – only on one server.
If I open up the file explorer after creating a VPN connection and try to connect to \\server1 I only get the login prompt that won’t let me through. I’ve tried with my domain username as well as domain\username with no joy. If I try to connect to network share with \\server1.domain.local I’m allowed through. If I use server1’s IP address I can connect to it.
This is the part where it gets tricky: Every other workstation & server in the network is accessible using their hostnames without the .domain.local part. On top of that I can ping server1 and it’s IP address gets resolved.
The server1 acts as a DC, DHCP server and DNS server in our network. Does this have some effect?
Cheers,
Mikko