Re: SBS 2003 BSOD when VPN client RDCs to in network XP machine.



On Jun 23, 8:31 am, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
DrewYK <drew_cush...@xxxxxxxxxxx> wrote:
I have a problem that I have not found even a hint of on the internet.

I recently went through hell and high water getting VPN up and running
on my network - mostly due to a bad DSL modem. Now I have a new
problem.

I have a machine that was setup at the office so that it could VPN
into the network and Remote Desktop to the users regular workstation.

In house all the tests were successful.

The user has the offsite machine setup at his house. He attaches to
the network using VPN and a login script runs successfully. He starts
RD and as the desktop of his workstation at the office begins to
appear on his screen the SBS 2003 server displays a BSOD.

Two other VPN users (at different locations with different PCs, one on
DSL the other on Cable) can connect and RD without causing the server
to reboot.

Where would you start troubleshooting this issue?

What does the BSOD say? It should give you clues.
Event log errors?
You've verified that his home network/PC does not use the same subnet as you
use in the office, I trust - although that shouldn't cause a BSOD, it will
cause problems.

The tests in the office were performed on a second network card in the
server. This allowed the VPN services the follow the same processes
that would be needed offsite. The other two VPN users were test
cases. One desktop unit and one Laptop. These machines did, and
continue to, work flawlessly.

The BSOD says the problem is with the servers NIC. The ONLY time the
BSOD occurs is when this third machine has already successfully
connected to the VPN and then an attempt is made to Remote Desktop
into the workstation assigned to them, in the office.

The reboot will occur regardless of how many other VPN users are
connected. (We originally thought it might have something to do with
my testing the VPN when they tried to access their desktop.) It occurs
only when this one station attempts RD regardless of the number of
other VPN users or any of them are using RD.

I temporarily told the user not to connect, changed the Laptops name
to match their machine name (at home) and logged into the VPN with the
users account. I then attempted to RD to the users machine. The
server did not reboot.

My next step, in my opinion, is to try my Laptop on his DSL connection
to see if I can get the server to reboot. This would tell me if there
is an issue on his end related to the service provider/DSL modem.

But this doesn't answer the bigger question: what about RD could cause
an SBS 2003 server to reboot?

.



Relevant Pages

  • 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)
  • Re: VPN with SBS 2003 (not R2) and DSL.
    ... Reading property value for VPN returned OK ... Reading VPN Server Name returned OK ... identical network cards. ... it seems doubtful that SBS will work properly with two NICs ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... on the SBS 2003 server just not sure where to go for help on it. ... Next time I'm at my home PC, I'll VPN in and see what IP info I'm getting ... client PC on your LAN, you should be able to do so from a remote VPN client, ... get the network path was not found. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Error 800
    ... The VPN client IP is 10.0.1.40, this is a private IP address. ... server IP address is 81.137.105.244, this is a Internet IP address. ... not test VPN connection from your perimeter network. ... SBS on your switch to make it work. ...
    (microsoft.public.windows.server.sbs)

Quantcast