I have a remote user running Windows XP Pro and connecting to my SBS 2003 server with a 56k phone line. The remote computer has a printer connected
that I need to print to from the other computers on the network. The printer
is shared, and I am able to access it and ping the remote computer's name
from the SBS server, but I CANNOT access the printer share. I CAN ping the
IP of the remote computer from the computers on the LAN, but I CANNOT ping
the computer name. Howerver, I DO need access to the printer on the
remote computer directly from the other computers on the LAN. How is the
best way to gain access to the shared printer?
Re: Printing to remote printer ... > Thank you for posting to the SBS Newsgroup.... Is remote computer a SBS 2K3 domain computer? ... Remote Desktop sessions to Windows Server Standard 2003 which is on the same ... > capture a screen shot for the error message, and send it to the Newsgroup.... (microsoft.public.windows.server.sbs)
Re: Application server slow down on a SBS 2003 network ... Maybe install TightVNC on your remote computer and on his machine. ...server gets happy again. ... his IE session is 4-5 times larger than any other user. ...SBS to reboot it. ... (microsoft.public.windows.server.sbs)
Re: Network issue ...SBS 2 NICs no ISA ... We can ping the remote computer from the server and every workstation at the ... (microsoft.public.windows.server.sbs)
Re: Unable to Connect to Server/Client Desktop using RWW ... So the problematic remote computer has an ip address in hte ... same range as the external NIC on the SBS server AND the ... Here are the requested remote and SBS server ipconfig alls.... (microsoft.public.backoffice.smallbiz)
Re: RDP and pcAnywhere ... Now, I go to a remote computer and do mstsc -v:servername -console to connect to the server using the same account, I will NOT see that My Documents folder opened. ... apparently the server created a separate session for me to connect remotely using the -console. ... The -admin switch works as well, but I didn't see a difference, but then again, I was only connecting to a session I had previously had opened under my own account, and have not tested it further to shadow another user's session by barrellin in, as the article implies. ... (microsoft.public.windows.server.general)
