Re: Remote Web Workplace question

Dave,

I went to the PCs and checked the domain under the firewall setting. They
are all on the domain.

Anything else I can do?

"Dave Nickason [SBS MVP]" wrote:

I would really look at the Windows Firewall thing I described. I'm not sure
how prevalent that is, but I've had it on at least 3 or 4 client PCs out of
26. It only takes a second to check, and if it's the issue, another second
to fix. The fact that some of your desktops are responding normally makes
this even more likely to be the cause IMO.


"GTP" <GTP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4A16F1D4-E3C4-48D2-AA21-50CC44D2E97A@xxxxxxxxxxxxxxxx
Dave,

Well, as it turns out, some PCs I can log into which is strange. All of
the
systems on the network are old systems, in other words, no new changes
have
occurred. I went to the systems that worked and compared them to the
systems
that do not work and on the systems, all the settings were the same. I
guess
what I will do is on the server re-run the user permissions, or, should I
try
the things you mentioned now that we know that we can login on some of the
systems?

Thanks,
Greg

"Dave Nickason [SBS MVP]" wrote:

So you can connect and log into RWW from any computer (internal or
external)
as always, but once you're in, you are blocked from logging into the
desktop
PCs? And this happens with every client PC on the network? Even when
attempting to log in with a domain administrator account?

And what happens if you try to access one of these client PCs from
another
within the LAN, using the remote desktop client instead of RWW? (On the
Start menu, it's Remote Desktop somewhere under Accessories). If you get
an
error message, please post back the exact text.

I'd still look at the firewall settings on one of the effected client
PCs.
Two things - remote desktop needs to be enabled in the Windows Firewall.
It
is by default in SBS, but it's worth a check. Secondly, if the firewall
starts before the Network Location Awareness service starts, it will use
the
non-domain settings, as I described previously, which block remote access
to
the PC. So there are two similar but different ways the Windows Firewall
can block remote access. I doubt that NLA thing would apply to every PC
in
your network, but it's a 2 second thing to rule out.

Another thing that could somehow have happened is that the individual
user(s) could have been removed from those authorized to access the
system
remotely. However, that should give a different error message than you
reported. Again, it only takes a couple of seconds to check in CP ->
System, on the Remote tab.


"GTP" <GTP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C0E5E969-EC0C-4F6C-929D-E497133CF646@xxxxxxxxxxxxxxxx
I don't think you are understanding. RWW was working just fine and has
been
for the last 3 years. I reran the ICW and the RCW. The problem is that
when
used internal or external of the network, using the
https://mail.server.com/remote url. The certificate ino comes up as it
should, A login screen allows us to enter the RWW. Once in we can us
Outlook.
We cannot login to our desktops.

I don't think that going around to each desktop is going to accomplish
anyhting since we didn't change anything. The domain profile has not
changed.
All ports on the router 444 and 4125 are open.

What is the deal????
Thanks,
Greg

"Dave Nickason [SBS MVP]" wrote:

First, see if you can log into one of the PCs from another on your
local
network. If you can use RWW normally from your own desktop PC, I'd
look
at
ISA or whatever firewall device you have at the network perimeter.

If you get the same error from within your network, go to the target
workstation and go to CP -> Windows Firewall. At the bottom of the
first
tab, see if it says it's using the domain or non-domain profile. If
non-domain, change the startup type for the Network Location Awareness
service to Automatic and reboot. You should then be able to connect,
in
which case just set NLA to automatic on the rest of the workstations
and
reboot them (gpupdate /force should have the same effect as a reboot
if
NLA
is running).


"GTP" <GTP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E69FEE2C-1629-43BD-9903-991D3DF9E7CB@xxxxxxxxxxxxxxxx
Hello,

I am having a proplem logging into anmy of our company computers
when
using
our https://mail.company.com/remote web address.

The error says that "Connectivity cannot be established" and to make
sure
the remote computer is on, which it is. There is no problems
internally,
and
on can use the "Outlook web access" remotely.

The system was working fine and I believe it failed after I
installed
some
updates not to long ago. It appears all services are runningh
correctly.

What should I look into?

Thanks,
Greg









.

Relevant Pages

  • Re: Home Network -- 2 XP Machines
    ... You said TWO XP PCs... ... which included firewall too. ... you'll need to look for them on "entire network". ... Use only one protocol for File and Printer Sharing. ...
    (microsoft.public.windowsxp.network_web)
  • Re: IP problem
    ... I disable Norton Firewall on the individual Machines, run Network Diagnostic ... All PCs assign unique names, ... 2 Desktops attached to Router ports. ...
    (microsoft.public.windowsxp.network_web)
  • Network problem
    ... local network. ... Now the IT Operations PCs are across the other side of a firewall & we ... You can connect to a remote PC using Computer Management and ...
    (microsoft.public.windowsxp.general)
  • Re: Modem with NAT firewall, do I also need a software firewall?
    ... Network Address Translation firewall and Stateful Packet ... Zonealarm installed. ... Windows XP Firewall is enabled, ... And, if you have multiple PCs behind a router, the inbound protection of ZA ...
    (microsoft.public.windowsxp.hardware)
  • Re: Cant access PC on home network
    ... that must be config'd on all PCs on a home network? ... caused by 1) a misconfigured firewall; ... user's account) for convenience, you can do this. ...
    (microsoft.public.windowsxp.network_web)