WUGNET, the Windows User Group Network
Your Complete Resource Center for "The Best" in Shareware, Computing Tips and Support, Windows Industry News... and much more!
Home Forums Shareware Windows Tips Hot Offers FREE Newsletters Arcade Contact Us About Partners
Search WUGNET: RSS Feeds RSS Feeds Advertise with WUGNET    |    Shareware eBooks
HomeHome FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

How to determine if a client is Local or Remote

 
   Home -> Windows Other -> Terminal Server RSS
Next:  Profile redundancy planning  
Author Message
Tim O'Pry

External


Since: Apr 02, 2006
Posts: 1



(Msg. 1) Posted: Sun Apr 02, 2006 1:11 pm
Post subject: How to determine if a client is Local or Remote
Archived from groups: microsoft>public>windowsnt>terminalserver>misc (more info?)

For the purposes of customizing the logon script, we need to be able to tell
if a client connecting to a terminal server session is local (on the LAN) or
remote.

While I can use the WTSManager COM object to return the client's IP, this is
of limited value. Most remote clients use a router and some are using the
same subnet as our LAN (192.168.x.x). To help with this, I have been doing
an NSLookup on the IP, getting the machine name and comparing that to the
WTSManager clientname. However, it is still possible that the machinename
could match the IP on the LAN (especially for remote offices).

I noticed that SecureRDP will return in the log the MAC address- only for
local clients. So this would also serve as a method to tell local from
remote. But, I cannot find the method SecureRDP is using to return this
info, or if the remote IP happens to match one on the LAN if it would return
the MAC for the local device (simply doing a lookup).

Is there a reliable way to determine if the client is remote?
Back to top
Login to vote
Mike

External


Since: Apr 21, 2005
Posts: 6



(Msg. 2) Posted: Wed May 31, 2006 11:50 am
Post subject: Re: How to determine if a client is Local or Remote [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi Tim,

I Don't think that the clients could be shown as 192.168.x.x because this is
a non routeable address (the outside world does not see it unless there is
custom software on both the client and server) the Terminal server will most
likely see the routable address assigned from the ISP to the clients router,
and then all traffic is sent from the TS server to that address and the NAT
software on the client router is going to forward the data to 192.168.x.x
address

This would be the normal function for SOHO routers like the Netgears Linksys
and D-link and things like that on an everyday "Follow the wizzard or user
manual" setup.

MAC addresses are two parts one part indicates the Vender like 3com Intel
etc. the next part is supposed to be unique or atleast it used to be.
Some bits of kit I have seen allow the MAC address to be changed so I am not
so sure anymore.

Mike


"Tim O'Pry" <topry RemoveThis @nospam.com> wrote in message
news:%23a4QFinVGHA.2360@TK2MSFTNGP09.phx.gbl...
> For the purposes of customizing the logon script, we need to be able to
> tell if a client connecting to a terminal server session is local (on the
> LAN) or remote.
>
> While I can use the WTSManager COM object to return the client's IP, this
> is of limited value. Most remote clients use a router and some are using
> the same subnet as our LAN (192.168.x.x). To help with this, I have been
> doing an NSLookup on the IP, getting the machine name and comparing that
> to the WTSManager clientname. However, it is still possible that the
> machinename could match the IP on the LAN (especially for remote offices).
>
> I noticed that SecureRDP will return in the log the MAC address- only for
> local clients. So this would also serve as a method to tell local from
> remote. But, I cannot find the method SecureRDP is using to return this
> info, or if the remote IP happens to match one on the LAN if it would
> return the MAC for the local device (simply doing a lookup).
>
> Is there a reliable way to determine if the client is remote?
>
>
Back to top
Login to vote
Display posts from previous:   
       Home -> Windows Other -> Terminal Server All times are: Eastern Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
Categories:
 Windows XP
 Windows Vista
  Windows Other
 Office
 Office Other
 Security
 WinRAR
  • Home |
  • Shareware |
  • Windows Tips |
  • Hot Offers |
  • FREE Newsletters |
  • Arcade |
  • Forums |
  • eBooks |
  • About WUGNET |
  • Partners |
  • Contact

  • WUGNET Privacy Policy |
  • Link to WUGNET