Re: Remote Web Workplace connects to wrong desktop

can you post a link to the web pages that brought you here? because you must be missing something there or we'll ask for it to be corrected.
SG pointed you over to the correct NG BECAUSE that's where the people who are engaged to monitor for Technet Subscribers are hanging out.
If you look through the responses here, you don't see anyone with MSFT or MS after their name, do you?

But you'll find lots of them over in the one SG pointed you to.

And if you're not any more willing to post the requested information for those trying to assist you over there than you were here, you're not likely to get very far in resolving your issue.

If your AD and DNS were working perfectly, then you wouldn't be having the issue you're having. AD Computer Accounts which is what provides the lists of workstations available for RWW connections and then DNS and WINS tell the network how to resolve that name to and IP address.

So somewhere you have some stale records in either DNS or WINS as SG tried to suggest to you. Do you have a PC on the network with a computer name that used to be long to another PC?

If you don't want other community members to respond to your posts, only MS reps, then perhaps you should indicate that at the beginning of your post

--
Cris Hanna [SBS-MVP]
------------------------------
Please do not contact me directly, only respond in the Newsgroups
MVPs do not work for Microsoft
------------------------------
Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2
"Allen Clark" <nospamacent1@xxxxxxxxxxxxxxxx> wrote in message news:E0551471-1F19-4967-B4DF-EC7A653F0A9D@xxxxxxxxxxxxxxxx
First: With a Technet Plus subscription, there are "Managed Newsgroups" that
are, by contract, supposed to be monitored and "managed" by Microsoft or
their representatives. On the web pages that this program presents to
fulfill the contractual obligations of this "benefit" there is ONLY this
newsgroup for Small Business Server. If you have problems with the posts
that are presented in this newsgroup seeking support for SBS, then see the
good people that run the TechNet Plus services and websites and complain to
them.

Second, DNS is configured perfectly. AD is fully functional and every
diagnostic that can be run against the network and Active Directory pass with
flying colors. All network services are configured correctly according to
all diangostics run.

Does anyone have any other ideas on how the wrong system is being connected
when the desired system is not turned on or is in sleep mode?

Thanks,
Allen

--


"SuperGumby [SBS MVP]" wrote:

first:

SBS public Newsgroups:

SBS 4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

but meanwhile I expect it's DNS related, DNS on the server may not be being
updated with the current IP of workstations. The most likely reason would be
an error in the IPConfig of either the server or workstations so when
posting to the SBS2003 group please include the output of 'ipconfig /all >
c:\ipconfig.txt' from both the server and one affected workstation.

"Allen Clark" <nospamacent1@xxxxxxxxxxxxxxxx> wrote in message
news:B7E48681-4A3E-476A-ACAD-F21B57DD65A5@xxxxxxxxxxxxxxxx
>I have a client running SBS2003 (not R2) and their users have a problem
> connecting to their desktop from the Internet via Remote Web Workplace.
> From
> the menu, they select their workstation, but they are connected to a
> different workstation. This is very frustrating because a person may > be
> working at their desktop, then they get kicked off when the remote user
> attempts to access the desktop in the remote users office, NOT the
> computer
> that was in use by the person in the office. I have checked the KB and
> have
> not seen anything about this. Has anyone else run into this issue? If
> so,
> how has it been resolved?
>
> Thanks,
> Allen
>
>




.

Relevant Pages

  • Re: fso roles
    ... Remove the second DNS from your SBS and either activate DHCP on all ... workstations or remove the DNS 10.0.0.2 from all workstations. ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW not connecting to remote computer
    ... I have checked and the computer in question does have the "allow users to connect remotely to this computer" checked and rww is setup correctly on SBS. ... That settles whether the problem is with the workstation or with the SBS, possibly due to some old DNS information. ... I've seen an XP workstation start refusing RWW/RDC connections, with no configuration change, and being fixed by rebooting. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2000 domain, XP Pro SP2 clients getting NETLOGON error
    ... Good old Server 2000 DC's using RRAS / VPN connections had the tendancy to ... Check the DNS entries for the SRV records and see if they are for the ... I have no other SBS 2000 domains to which I ...
    (microsoft.public.windows.server.sbs)
  • Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
    ... The following error occurred when DNS was queried for the service location ... What happens if you just turn the SBS 2000 off or remove it from the wires. ... Errors in your event logs on the workstations or W2k3 server? ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
    ... The following error occurred when DNS was queried for the service location ... Errors in your event logs on the workstations or W2k3 server? ... the workstations still know anything about the old SBS 2000 ISA server. ...
    (microsoft.public.backoffice.smallbiz2000)