From: Joe Welna on
Check that remote desktop is open in the local firewall. I had one
workstation that had that port closed in Windows firewall by an anti-malware
program (SDFix I believe) even though remote desktop was unchecked/checked.
It certainly was a hair puller to finally figure that out. If that doesn't
work, turn off all local firewalls, especially any associated with Norton
Interet Security.

Still a nogo, try re-installing TCP/IP on that system. I've had malware
really damage transport layers that couldn't be repaired manually.

"Northwest Upgrades Plus" wrote:

> I have a client that has run in to a snag. THy are running SBS 2003 Standard.
> They have 14 workstations of which all are able to be connected to remotely
> by the Administrator with the exception of one machine. The Allow Remote
> Users has been unchecke, applied and rechecked and applied but that did not
> help. There is nothing different with the one machine than any of the others.
> Please help as I am stuck on this one and I need to be able to remote in so I
> can do updates, etc. And also so the client can work remotely from home.
> --
> Thanks for your help.
From: SteveB on
What is the original post with day and time you're replying to?

"Joe Welna" <JoeWelna(a)discussions.microsoft.com> wrote in message
news:4464EF92-7580-496E-BFC7-7681AF1E3315(a)microsoft.com...
> Check that remote desktop is open in the local firewall. I had one
> workstation that had that port closed in Windows firewall by an
> anti-malware
> program (SDFix I believe) even though remote desktop was
> unchecked/checked.
> It certainly was a hair puller to finally figure that out. If that doesn't
> work, turn off all local firewalls, especially any associated with Norton
> Interet Security.
>
> Still a nogo, try re-installing TCP/IP on that system. I've had malware
> really damage transport layers that couldn't be repaired manually.
>
> "Northwest Upgrades Plus" wrote:
>
>> I have a client that has run in to a snag. THy are running SBS 2003
>> Standard.
>> They have 14 workstations of which all are able to be connected to
>> remotely
>> by the Administrator with the exception of one machine. The Allow Remote
>> Users has been unchecke, applied and rechecked and applied but that did
>> not
>> help. There is nothing different with the one machine than any of the
>> others.
>> Please help as I am stuck on this one and I need to be able to remote in
>> so I
>> can do updates, etc. And also so the client can work remotely from home.
>> --
>> Thanks for your help.


From: Joe Welna on
3/22 8:01P

"SteveB" wrote:

> What is the original post with day and time you're replying to?
>
> "Joe Welna" <JoeWelna(a)discussions.microsoft.com> wrote in message
> news:4464EF92-7580-496E-BFC7-7681AF1E3315(a)microsoft.com...
> > Check that remote desktop is open in the local firewall. I had one
> > workstation that had that port closed in Windows firewall by an
> > anti-malware
> > program (SDFix I believe) even though remote desktop was
> > unchecked/checked.
> > It certainly was a hair puller to finally figure that out. If that doesn't
> > work, turn off all local firewalls, especially any associated with Norton
> > Interet Security.
> >
> > Still a nogo, try re-installing TCP/IP on that system. I've had malware
> > really damage transport layers that couldn't be repaired manually.
> >
> > "Northwest Upgrades Plus" wrote:
> >
> >> I have a client that has run in to a snag. THy are running SBS 2003
> >> Standard.
> >> They have 14 workstations of which all are able to be connected to
> >> remotely
> >> by the Administrator with the exception of one machine. The Allow Remote
> >> Users has been unchecke, applied and rechecked and applied but that did
> >> not
> >> help. There is nothing different with the one machine than any of the
> >> others.
> >> Please help as I am stuck on this one and I need to be able to remote in
> >> so I
> >> can do updates, etc. And also so the client can work remotely from home.
> >> --
> >> Thanks for your help.
>
>
> .
>