Re: Unable to Connect to Server/Client Desktop using RWW
- From: "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Jul 2008 17:32:11 -0400
Please post the results of an ipconfig /all for the sbs server.
--
Merv Porter [SBS-MVP]
============================
"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:12C42E24-6DA5-4DD2-95F8-F68EAAB0338B@xxxxxxxxxxxxxxxx
Hello Merv.
This problem occurs on IE6 and IE7. I tried it on various wired remotes,
never wireless.
I did another test after turning off the firewall on the remote. I
checked
the Application and System events for both the remote and the server.
There
are no errors for the period of time that a failed connect was attempted.
Thanks,
Tony
"Merv Porter [SBS-MVP]" wrote:
Port 4125 only needs to be forwarded to the external NIC IP address on
your
SBS server. However, some 3rd party firewalls (like Norton's) on the
remote
machines may be blocking communications with the target LAN workstation
or
server.
When a remote user cannot connect, asre there any errors listed in the
event
logs of the SBS server or of the target LAN workstation?
Are all the remote workstations using Internet Explorer 6 or are they
using
IE7?
Are the remote machines using wired or wireless connections?
--
Merv Porter [SBS-MVP]
============================
"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:6C8AA318-F2FC-40CC-9CFC-BF3B257E2C17@xxxxxxxxxxxxxxxx
Hello Merv.
Ok. That much is done. Port 4125 is forwarded on my router to the ip
address of the sbs external two nic setup.
If port 4125 was not forwarded on the sbs machine, wouldn't that mean
that
none of the remotes would work?
On any of the remote machines where this problem does NOT occur, i
don't
see
port 4125 being opened or forwarded or anything. So, if it works OK on
a
machine that has no exceptions for port 4125, doesn't that mean that
port
4125 is not an issue?
Thanks,
Tony
"Merv Porter [SBS-MVP]" wrote:
With port 4125 and SBS, "opening it" generally means to use 'port
forwarding' in the router to direct traffic on port 4125 to the SBS
Internal
NIC IP address (if a single NIC SBS server) or to the External SBS NIC
IP
address (if you have a 2 NIC SBS server).
On the remote computers, their may be software firewalls or routers
which
may be blocking traffic on port 4125.
Port Forwarding (for various routers)
http://portforward.com/english/routers/port_forwarding/routerindex.htm
--
Merv Porter [SBS-MVP]
============================
"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:94BF7476-B3EA-400E-9FC3-139C20AC7D15@xxxxxxxxxxxxxxxx
Hello Merv.
Thanks for the link to sbs newsgroups. I wish there was a list like
that
for newsgroups in news.microsoft.com.
Ports. I tested for port 4125 on a couple of sites that test for
open
ports. Each site indicated that port 4125 was not open. However, i
tested
it on both computers that have the connect problem as well as
computers
that
don't have the connect problem.
So, i'm not sure of what ports are all about. When they say that
you
need
to open a port, how do you do that?
Thanks,
Tony
"Merv Porter [SBS-MVP]" wrote:
Hi Tony,
A little more info about the SBS newsgroups
The SBS Newsgroups Posting FAQ
http://www.sbs-rocks.com/Netiquette.htm
Sounds like port 4125 may be blocked by the remote machines (by
installed
firewall or router).
--
Merv Porter [SBS-MVP]
============================
"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:uMD2ZpQ8IHA.1428@xxxxxxxxxxxxxxxxxxxxxxx
Hello Larry.
Thanks for your help.
I wish there was a list of newsgroup names and what they are used
for.
When i tried the remotes, i tried both public and non-public.
Either
way
gives the same results. I have the seen the ActiveX control
problem.
This is not the same thing because there is no error and no
indication
of
any messages where it is looking for something.
Thanks,
Tony
"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@xxxxxxxxxxxxxxx>
wrote
in
message news:%23zsYEhQ8IHA.3480@xxxxxxxxxxxxxxxxxxxxxxx
You might get more "eyes", and therefore more response in the
SBS
2003
group.
microsoft.public.windows.server.sbs
Are the remotes that fail public computers? Could they have a
policy/firewall that prohibits ActiveX controls from being
installed?
-Larry
"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:uwGyBXQ8IHA.4988@xxxxxxxxxxxxxxxxxxxxxxx
Hello.
SBS2003, SP2, Exchange, ISA2004, SQL Server 2005, SharePoint
2.0,
Two
nics, router, switch, DynDNS static IP, FIOS Internet.
When i attempt to use RWW from a remote computer by going to
https://xxxxxxxx.DynDNS.Org/Remote, after logging in as
administrator, i
get the RWW menu of:
Connect to Server Desktops
Connect to Client Desktops
Monitor Help Desk
Administer the company's internal Web site
View server performance report
View server usage report
Every option on this screen works, no matter where i am
remotely,
except
when i attempt to Connect to Server Desktops or Connect to
Client
Desktops it brings me to the list of servers(we only have one)
or
the
list of client computers. When i select one and click Connect,
it
does
nothing but give me a blank RWW screen with just the Log Off
and
Main
Menu options.
No error occurs. It just does nothing.
This only happens on some remote computers. All remote
computers
that i
tried it on have Windows XP SP2(not SP3). Some of them work
but
others
give the results explained above and i can't figure out what is
different on the remote computers that are connecting as
opposed
to
the
remote computers that don't connect.
I ran CEICW on the server several times.
Any help in resolving this issue would be gratefully
appreciated.
Thanks,
Tony
.
- Follow-Ups:
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Merv Porter [SBS-MVP]
- Re: Unable to Connect to Server/Client Desktop using RWW
- References:
- Unable to Connect to Server/Client Desktop using RWW
- From: Tony Girgenti
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Larry Struckmeyer [SBS-MVP]
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Tony Girgenti
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Merv Porter [SBS-MVP]
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Tony Girgenti
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Merv Porter [SBS-MVP]
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Tony Girgenti
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Merv Porter [SBS-MVP]
- Re: Unable to Connect to Server/Client Desktop using RWW
- From: Tony Girgenti
- Unable to Connect to Server/Client Desktop using RWW
- Prev by Date: Re: Unable to Connect to Server/Client Desktop using RWW
- Next by Date: Re: Unable to Connect to Server/Client Desktop using RWW
- Previous by thread: Re: Unable to Connect to Server/Client Desktop using RWW
- Next by thread: Re: Unable to Connect to Server/Client Desktop using RWW
- Index(es):
Relevant Pages
|