Re: Problems after SP2

I've tried RWW to the server from domain-joined client PC over the LAN and remotely over VPN from a non-domain-joined pc, neither work.

I had to set Default Website/Remote ASP.NET back to v2 because CompanyWeb is stuck at V2 (pull down is disabled) and I get application event error when trying to run RWW with these at two different versions.

RWW to desktop works!

I found this tidbit at http://blogs.technet.com/sbs/archive/2007/06/01/unable-to-rdp-rww-into-the-sbs-server-after-applying-sp2.aspx

"If you are unable to RDP/RWW (i.e. to connect using Terminal Services) into your SBS server after applying Windows Server 2003 SP2, then check to see if the server is even listening on TCP Port 3389 (default port). "

"If it simply comes back to the command prompt after entering the netstat –aon | find “:3389” then it would appear that the Terminal Services is not listening on its default port. "
this is the case when I run netstat. the port is not found all I get is the command prompt.

"We are still investigating this issue, however, one workaround is to simply log on to the console on the server itself and re-apply Windows Server 2003 SP2"
Which of course means takeing yet another backup of the server and more downtime.

I might run up this Saturday to try and re-install SP2.

Michael


Can you RDP into the server from a domain-joined client PC over the
LAN? Or from the remote PC after connecting over VPN?

Can you connect to RWW and then remote to a client PC, or is this
effecting clients and server?

"Dabbler" <Dabbler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:105D4F44-AB43-4D74-882F-AD7324A7CE13@xxxxxxxxxxxxxxxx

Hi Dave,

Well, I'm back at the client. Installed Exchange SP2, Sharepoint SP1,
SBS
SP1, Vista compatiblity etc with the only notable failure being
Outlook
2003
SP1 which we don't care about.
RWW still doesn't work. Testing as Domain Administrator, RWW is
enabled.
BPA
notified that RWW wasn't using ASP.NET v1 so I changed it from
ASP.NET v2.
CompanyWeb got the same complaint but the setting is disabled so it's
stuck
at v2.
Any other suggestions would be appreciated.

Thanks!

Michael

"Dave Nickason [SBS MVP]" wrote:

For RWW, I'm assuming you've checked the basics? It's enabled on
the
SBS,
the account you're logging in with has the appropriate rights,
nothing
noteworthy in the logs?
"Michael Appelmans" <news@xxxxxxxxxx> wrote in message
news:384112b30baf8caa0152aeeb3a0@xxxxxxxxxxxxxxxxxxxxxxx

Thanks Dave. I went to the site yesterday and did another shutdown
which
installed some 34 updates. After that BPA showed only a couple of
critical
issues, the only significant one remaining is SBS SP1. Since it
failed
to
install last time we tried it I think I'll just skip it and forge
ahead
with the Swing Migration to the new server.
RWW still does not work, reporting the same error ""Connectivity to
the
remote computer could not be established."
Thanks for your suggestions.

Michael

You can install the SBS-specific parts of the service pack even on
the machine that's already at SP2. Just don't install Windows
Server SP1 (as opposed to SBS SP1, which is a different thing that
also includes the Windows Server SP). Just skip anything that's
already been installed, or had a newer version installed. As you
say, SP's are cumulative, but we're referring to SBS-specific
updates that are not part of the Windows SP, so they're not
included in SP2.

As stated in the KB I posted earlier, any issues caused by Windows
Server SP2 should be fixed by just running WSUS or MU. I agree
that it's unfortunate you have to go to the site, but I recommend
only installing SPs remotely if you're able to get to the server
if necessary. I agree that it shouldn't happen, but I'm not
surprised it did, especially with something as major as a service
pack.

I'm thinking that installing the networking updates from the KB is
going to fix everything - please post back your results in case
someone runs into this in the future.

"Michael Appelmans" <news@xxxxxxxxxx> wrote in message
news:384112b309d08ca9e9f891c7bf0@xxxxxxxxxxxxxxxxxxxxxxx

You suggested installing SBS-specific portions of SP1. Can I
install this after I've installed SP2? I though SP's were
cummulative? VPN and remote DCOM+ are working again for eveyone.

RWW still doesn't work. Neither does CrossLoop to desktops, this
was working before (we no longer use Remote Assistance, it's hit
or miss connecting only about half the time we attempt it).

Error: "Connectivity to the remote computer could not be
established.
Ensure that the remote computer is on and is connected to the
Small
Business
Server network."
Guess I'll have to burn some precious gas and make a trip out to
my
client
to try and fix RWW... was hoping to avoid this. Why do service
packs
always have to break something that was already working?? I
thought
the
whole premise of SBS was that it wouldn't need a nursemaid.
Sorry...
can
you tell I'm peeved?
Thanks for any help.
Michael

You need to apply the SBS-specific portions of SP1. You don't
need to actually install Windows Server SP1, but you do need the
SBS parts. See also:

Windows 2003 service pack 2 known issues on Small Business
Server 2003 http://support.microsoft.com/kb/555912

You might also consider running the SBS BPA from
http://support.microsoft.com/kb/940439/en-us.
If you're still running into problems after that, please post
back
the details of what you see when RWW fails. As for the COM
error,
when you click the link in the error message, you usually get
detailed instructions for fixing the permissions. Any help
there?
"Michael Appelmans" <news@xxxxxxxxxx> wrote in message
news:384112b309108ca9dbb58affdf0@xxxxxxxxxxxxxxxxxxxxxxx

Installed SP 2 on SBS 2003 Standard with no SP (SP1 failed to
install a long time ago, just tried SP2 due to imminent Swing
Mirgration which requires SPs, SP2 installed succesfully)

Now RWW and a COM+ application doesn't work. COM+ application
returns "error #70 - permission denied" although we haven't
done anything with permissions on the server since SP2 install.

Hope someone can suggest a solution asap.

Michael



.

Relevant Pages

  • Re: RWW
    ... "normal" Windows Server 2003 way... ... that this worked before trying RWW in this environment. ... enable Remote Desktop first and to add to the local Remote Desktop Users ... as well as entering credentials on the FBA logon page. ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Access
    ... internet in services configuration page. ... 825763 How to configure Internet access in Windows Small Business Server ... Also please check the RWW site settings: ... Right click Remote and click Properties. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Connection Issue
    ... the main reason many inidividuals went to 2003 is the RWW (remote web ... > If you want to connect to connect to the SBS server box and the LAN client ... >>through port number 3389 and a workstation on the LAN through port number ...
    (microsoft.public.windows.server.sbs)
  • RE: document spools then disappears in Remote printing in RWW
    ... then access RWW site and then connect to the server box to print? ... The remote machine ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 VPN question.
    ... it is quite likely Dana will need to figure out how to forward port 4125 in order to use the ... Then, to set up RWW, you start up CEICW, select your services. ... Then on the Web Server Certificate page, Create a New Web Certificate and enter "server1.danaco.com". ... The remote user will need an SBS User CAL, whether he uses VPN or RWW. ...
    (microsoft.public.windows.server.sbs)