Logon through terminal services produces wrong desktop PC +

[Guest]

First question:
I have a user who uses a computer we will call "PC1" At work, his logon
goes along with PC1. At home, when he tries to logon to his computer through
Remote Web Workplace, he clicks on Connect To My Computer At Work, and his
computer does not show up. Instead he is directed to PC2. He is unable to
switch to his PC, PC1. All of the desktop PC's and his home PC are Windows
XP Pro, with SP2.

Second question:
Another user logs onto the network. He is unable to connect to the network
printers or access the network drives. When I log on as Administrator, I am
able to access the resources. Had him try from another computer, and he was
able to access the resources. Now here is a biggie, our security logs show
that someone is using his PC to hack into the network. While the computer is
unplugeged, the logon erros are gone. I have the PC in my office, plugged it
in, and we once again had the log on errors in the securtity logs.

I checked for Spywear and viruses and it came up clean.

What can be done with both computers?

 

[Charlie Tame]

First question:
I have a user who uses a computer we will call "PC1" At work, his logon
goes along with PC1. At home, when he tries to logon to his computer
through
Remote Web Workplace, he clicks on Connect To My Computer At Work, and his
computer does not show up. Instead he is directed to PC2. He is unable
to
switch to his PC, PC1. All of the desktop PC's and his home PC are
Windows
XP Pro, with SP2.

Second question:
Another user logs onto the network. He is unable to connect to the
network
printers or access the network drives. When I log on as Administrator, I
am
able to access the resources. Had him try from another computer, and he
was
able to access the resources. Now here is a biggie, our security logs
show
that someone is using his PC to hack into the network. While the computer
is
unplugeged, the logon erros are gone. I have the PC in my office, plugged
it
in, and we once again had the log on errors in the securtity logs.

I checked for Spywear and viruses and it came up clean.

What can be done with both computers?

Not sure I am understanding you completely but let's say at work there are
two computers and a router. To the internet, both computers will "Appear" to
have the same IP Address but to use remote desktop the router will have to
set to open the correct "Port" and it will only be able to do this for one
of the two machines, thus any attempt to go via remote desktop from the
outside will always go to the desktop of that machine. The default port is
3389.

To choose the other machine you will have to give it a different port for
remote access, and also probably set this port open on the router.

http://support.microsoft.com/default.aspx?scid=kb;en-us;306759

So now when you connect from outside, let's say your IP address is
xxx.xxx.xxx.xxx you will get the default machine using both.
xxx.xxx.xxx.xxx
or
xxx.xxx.xxx.xxx:3389


Suppose you set the other machine to port 3390 you will get that machine
using
xxx.xxx.xxx.xxx:3390

For this machine you will always have to use the port number.

Note that this applies to connections from outside that only "See" a single
IP address, if you were connecting from one machine to the other "Inside"
your office you would not have to change port numbers because on the local
network the machines will have different IP addresses, but if you have to
get access from outside then you will have to change one port number and
this port number will also apply internally, so if you have been using
network names to connect while in the office than simply add a colon and the
port number.


As to the second question you lost me there, there will be log on errors if
there's a log on problem, and obviously there is if the user can't use parts
of the system, where does the subject of "Hacking" or "Virus/Spyware" fit in
to this? It may would help if you gave the actual error messages that show
up when he tried to log in and I guess it would help to know if you are
using a "Domain" or a workgroup. This just sounds like a user permissions
problem to me, but you may consider asking in one of the server groups to
get opinions from folks who do more of this kind of stuff every day at work




Charlie