Hi,

I'm having a weird remote access problem with a single PC on a 10 PC
LAN.

Running SBS 2003, all domain users can reliably remotely connect using
remote web workspace except one. All users are able to log on to RWW and
can then select "connect to my computer at work" but when this single
user does this he then gets the error "Connectivity to the remote
computer could not be established. Ensure that the remote computer is on
and connected to the Windows Small Business Network."

What is odd is that if I open port 3389 on the router and forward it to
the problem PC (thereby bypassing the server and port 4125), I can log
in using remote desktop connection flawlessly _*every_*_ time. In fact,
this user was initially using this method daily before RWW was enabled
for the others.

Sometimes, if I first directly connect using RDP on 3389, then log off
and then retry using RWW it will work. Hibernation is not enabled, the
NIC is not set to turn off...

I have configured a different PC for this user, albeit with the same
user account, and the exact same behavior still exists.

Any insight into this would be greatly appreciated!


-- 
techheads
------------------------------------------------------------------------
techheads's Profile: http://forums.techarena.in/members/170788.htm
View this thread: http://forums.techarena.in/small-business-server/1289591.htm

http://forums.techarena.in

Port forwarding to the problem PC's IP address is also bypassing DNS - where 
you probably have a stale DNS entry for the troublesome RWW pc.

techheads wrote:
> Hi,
>
> I'm having a weird remote access problem with a single PC on a 10 PC
> LAN.
>
> Running SBS 2003, all domain users can reliably remotely connect using
> remote web workspace except one. All users are able to log on to RWW
> and can then select "connect to my computer at work" but when this
> single user does this he then gets the error "Connectivity to the
> remote computer could not be established. Ensure that the remote
> computer is on and connected to the Windows Small Business Network."
>
> What is odd is that if I open port 3389 on the router and forward it
> to the problem PC (thereby bypassing the server and port 4125), I can
> log in using remote desktop connection flawlessly _*every_*_ time. In
> fact, this user was initially using this method daily before RWW was
> enabled for the others.
>
> Sometimes, if I first directly connect using RDP on 3389, then log off
> and then retry using RWW it will work. Hibernation is not enabled, the
> NIC is not set to turn off...
>
> I have configured a different PC for this user, albeit with the same
> user account, and the exact same behavior still exists.
>
> Any insight into this would be greatly appreciated!

-- 
/kj 

There was an old DNS entry...but although I corrected it and rebooted
the same problem exists. This PC is using a static LAN IP so the RDP on
3389 can still be used, could that be the problem?


-- 
techheads
------------------------------------------------------------------------
techheads's Profile: http://forums.techarena.in/members/170788.htm
View this thread: http://forums.techarena.in/small-business-server/1289591.htm

http://forums.techarena.in

There was an old DNS entry...but although I corrected it and rebooted the 
same problem exists. This PC is using a static LAN IP so the RDP on 3389 can 
still be used, could that be the problem?

"kj [SBS MVP]" wrote:

> Port forwarding to the problem PC's IP address is also bypassing DNS - where 
> you probably have a stale DNS entry for the troublesome RWW pc.
> 
> techheads wrote:
> > Hi,
> >
> > I'm having a weird remote access problem with a single PC on a 10 PC
> > LAN.
> >
> > Running SBS 2003, all domain users can reliably remotely connect using
> > remote web workspace except one. All users are able to log on to RWW
> > and can then select "connect to my computer at work" but when this
> > single user does this he then gets the error "Connectivity to the
> > remote computer could not be established. Ensure that the remote
> > computer is on and connected to the Windows Small Business Network."
> >
> > What is odd is that if I open port 3389 on the router and forward it
> > to the problem PC (thereby bypassing the server and port 4125), I can
> > log in using remote desktop connection flawlessly _*every_*_ time. In
> > fact, this user was initially using this method daily before RWW was
> > enabled for the others.
> >
> > Sometimes, if I first directly connect using RDP on 3389, then log off
> > and then retry using RWW it will work. Hibernation is not enabled, the
> > NIC is not set to turn off...
> >
> > I have configured a different PC for this user, albeit with the same
> > user account, and the exact same behavior still exists.
> >
> > Any insight into this would be greatly appreciated!
> 
> -- 
> /kj 
> 
> 
> .
> 

If the PC is using a static IP then, even though you removed the old DNS 
entry, RWW may not be able to find the *correct* IP.  You'll need to create 
a DNS entry for the PC or allow DHCP to do so (thus removing the static IP.) 
Also, flushing the DNS cache on the server and the PC making the connection 
wouldn't hurt.  ipconfig /flushdns

-Cliff


"techheads" <techheads@discussions.microsoft.com> wrote in message 
news:D6B60625-1A62-45D0-B7D1-7CA3A8078C1C@microsoft.com...
> There was an old DNS entry...but although I corrected it and rebooted the
> same problem exists. This PC is using a static LAN IP so the RDP on 3389 
> can
> still be used, could that be the problem?
>
> "kj [SBS MVP]" wrote:
>
>> Port forwarding to the problem PC's IP address is also bypassing DNS - 
>> where
>> you probably have a stale DNS entry for the troublesome RWW pc.
>>
>> techheads wrote:
>> > Hi,
>> >
>> > I'm having a weird remote access problem with a single PC on a 10 PC
>> > LAN.
>> >
>> > Running SBS 2003, all domain users can reliably remotely connect using
>> > remote web workspace except one. All users are able to log on to RWW
>> > and can then select "connect to my computer at work" but when this
>> > single user does this he then gets the error "Connectivity to the
>> > remote computer could not be established. Ensure that the remote
>> > computer is on and connected to the Windows Small Business Network."
>> >
>> > What is odd is that if I open port 3389 on the router and forward it
>> > to the problem PC (thereby bypassing the server and port 4125), I can
>> > log in using remote desktop connection flawlessly _*every_*_ time. In
>> > fact, this user was initially using this method daily before RWW was
>> > enabled for the others.
>> >
>> > Sometimes, if I first directly connect using RDP on 3389, then log off
>> > and then retry using RWW it will work. Hibernation is not enabled, the
>> > NIC is not set to turn off...
>> >
>> > I have configured a different PC for this user, albeit with the same
>> > user account, and the exact same behavior still exists.
>> >
>> > Any insight into this would be greatly appreciated!
>>
>> -- 
>> /kj
>>
>>
>> .
>> 

If by "create a DNS entry for the PC" you mean entering primary and
secondary DNS server address entries in the TCP/IP properties sheet, yes
I have done that. Will try flushing the cache and report back. Thanks.


-- 
techheads
------------------------------------------------------------------------
techheads's Profile: http://forums.techarena.in/members/170788.htm
View this thread: http://forums.techarena.in/small-business-server/1289591.htm

http://forums.techarena.in

techheads wrote:
> There was an old DNS entry...but although I corrected it and rebooted
> the same problem exists. This PC is using a static LAN IP so the RDP
> on 3389 can still be used, could that be the problem?

A domain joined XP workstation by default should register it's own DNS 
record(s) and RWW should use this to locate the workstation.( No manual 
Static DNS records should be required) After verifying that there are no 
stale or duplicate A or PTR records for the workstation in DNS, then a DNS 
cache flush on the SBS server should fix this.

Nslookup tools can be used to verify resolution. I'm pretty sure that RWW 
uses DNS and not WINS to locate workstations, but if it still is 
problematic, then I'd check WINS.

>
> "kj [SBS MVP]" wrote:
>
>> Port forwarding to the problem PC's IP address is also bypassing DNS
>> - where you probably have a stale DNS entry for the troublesome RWW
>> pc.
>>
>> techheads wrote:
>>> Hi,
>>>
>>> I'm having a weird remote access problem with a single PC on a 10 PC
>>> LAN.
>>>
>>> Running SBS 2003, all domain users can reliably remotely connect
>>> using remote web workspace except one. All users are able to log on
>>> to RWW and can then select "connect to my computer at work" but
>>> when this single user does this he then gets the error
>>> "Connectivity to the remote computer could not be established.
>>> Ensure that the remote computer is on and connected to the Windows
>>> Small Business Network."
>>>
>>> What is odd is that if I open port 3389 on the router and forward it
>>> to the problem PC (thereby bypassing the server and port 4125), I
>>> can log in using remote desktop connection flawlessly _*every_*_
>>> time. In fact, this user was initially using this method daily
>>> before RWW was enabled for the others.
>>>
>>> Sometimes, if I first directly connect using RDP on 3389, then log
>>> off and then retry using RWW it will work. Hibernation is not
>>> enabled, the NIC is not set to turn off...
>>>
>>> I have configured a different PC for this user, albeit with the same
>>> user account, and the exact same behavior still exists.
>>>
>>> Any insight into this would be greatly appreciated!
>>
>> --
>> /kj
>>
>>
>> .

-- 
/kj 

Flushdns made no difference.

Just found that I cannot browse to this PC from the server - My
computer> my network places> entire network> microsoft windows
network>"domain">"thisPC"
Returns the error "\\thisPC is not accessible. You might not have
permission to use this network resource. Contact the administrator of
this server to find out if you have access permissions. The network path
was not found."

All of this user's apps (exchange, etc.) are working normally.


-- 
techheads
------------------------------------------------------------------------
techheads's Profile: http://forums.techarena.in/members/170788.htm
View this thread: http://forums.techarena.in/small-business-server/1289591.htm

http://forums.techarena.in

Ipconfig from both server and ws might help.

What about entries in WINS?

Remove any static entries you made in DNS for the workstation. Then go to 
the workstations and as an admin in a command prompt run;

ipconfig /registerdns

( you might also get the ipconfig for us while you are there)

Try \\thispc.domain.local instead

and;

nslookup
>set d2
>thispc.domain.local

(post results)

techheads wrote:
> Flushdns made no difference.
>
> Just found that I cannot browse to this PC from the server - My
> computer> my network places> entire network> microsoft windows
> network>"domain">"thisPC"
> Returns the error "\\thisPC is not accessible. You might not have
> permission to use this network resource. Contact the administrator of
> this server to find out if you have access permissions. The network
> path was not found."
>
> All of this user's apps (exchange, etc.) are working normally.

-- 
/kj 

No that is not what I mean.  I mean that, in the DNS server database, a 
record should exist for the machine.  It sounds like one used to, but with a 
bad IP, and you removed it.  Now *none* exists, so how is the SBS Server 
supposed to find and pass on the IP address of the machine you are trying to 
connect to?

-Cliff


"techheads" <techheads.44bt7c@DoNotSpam.com> wrote in message 
news:techheads.44bt7c@DoNotSpam.com...
>
> If by "create a DNS entry for the PC" you mean entering primary and
> secondary DNS server address entries in the TCP/IP properties sheet, yes
> I have done that. Will try flushing the cache and report back. Thanks.
>
>
> -- 
> techheads
> ------------------------------------------------------------------------
> techheads's Profile: http://forums.techarena.in/members/170788.htm
> View this thread: 
> http://forums.techarena.in/small-business-server/1289591.htm
>
> http://forums.techarena.in
>