Any workaround for adding workstations to domain over VPN?
From: Robert G. Smith (rsmith_at_resolutecorp.com)
Date: Mon, 19 Jul 2021 21:38:20 -0700
I've tried using the wizard that SBS sets up on
http://servername/connectcomputer and it's a nice utility. Problem is for
remote users who are VPN'd to the network using Microsoft VPN, it brings up
an error message about the "SBS Network Configuration Wizard will only run
over a Local Area Network connection".
Anyone come up with a way to trick it into working using Microsoft VPN?
Note: It works fine if you are using a different VPN service (such as your
firewall). It only quits if it detects Microsoft's VPN client running.
Yes, I can have users select My Computer, Properties and add their
workstations that way....but the /connnectcomputer utility looked much
easier for most users...until finding out it doesn't work remotely. The odd
thing...one of my users DID get it to work once using MS VPN client...but
has not been able to reproduce that.
- Re: Network NeighbourHood problem
... log in directly into the domain, without the need of VPN) An Microsoft ... remote
users do not appear in network neighbourhood on the server.. ... We have yet to set
the backup to occur on the remote users computers ... (microsoft.public.windows.server.sbs)
- How to add computer accounts remotely?
... I've tried using the wizard that SBS sets up on ... remote users who
are VPN'd to the network using Microsoft VPN, ... Anyone come up with a way to trick it
into working using Microsoft VPN? ... (microsoft.public.windows.server.sbs)
- Cached Credentials out of sync with Domain
... ELC has a VPN that uses SecureID Tokens to auth into our ... The remote users
login to a cached version ... connecting to our VPN are on our network, ...
cached credentials aren't updated unless they do a CTRL- ... (microsoft.public.windowsxp.security_admin)
- Set up cached credentials
... We have remote users that we want to VPN into the network using ...
something other than MS RRAS. ... (microsoft.public.windowsxp.security_admin)
- Re: [Full-disclosure] Remote Desktop Command Fixation Attacks
... This set of steps is redundant in many places, and it's also enormously expensive, since you're
using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator),
in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license.
... Your computers necessarily don't have full access to your network infrastructure when
they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to
be applied. ... Turning on, enabling, and implementing every possible security setting
and device you think of is not defence in depth, and will probably only have two effects - your users
won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful*
security measures. ... (Full-Disclosure)