|
||||||||
|
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|
When I try and map and/or remote desktop to one of our NAS's running Server
2003 I'm getting a network path not found. I can map to it via IP. From the NAS itself I can map to any pc on the network by name. There was some remote configuration going on when this stopped. Is there a service(s) or security policy setting I need to look at? Terminal services & RPC are running. -- Craig Craig |
|
#2
|
|||
|
|||
|
More information: I can use Remote Desktop using the IP address of the NAS.
The port 3389 state is listening. -- Craig "Craig" wrote: > When I try and map and/or remote desktop to one of our NAS's running Server > 2003 I'm getting a network path not found. I can map to it via IP. From the > NAS itself I can map to any pc on the network by name. There was some remote > configuration going on when this stopped. Is there a service(s) or security > policy setting I need to look at? Terminal services & RPC are running. > -- > Craig |
|
#3
|
|||
|
|||
|
"Craig" <(E-Mail Removed)> wrote in message news:9E09881B-1C13-4234-8DFB-(E-Mail Removed)... > When I try and map and/or remote desktop to one of our NAS's running > Server > 2003 I'm getting a network path not found. I can map to it via IP. From > the > NAS itself I can map to any pc on the network by name. There was some > remote > configuration going on when this stopped. Is there a service(s) or > security > policy setting I need to look at? Terminal services & RPC are running. > -- > Craig Hi Craig, generally when you can map to an IP address of a computer but not the computer name it means you have a DNS problem. That's where I'd start my investigation. |
![]() |
| Tags |
| 2003, desktop, map or remote, nas, running, server, sp2, unable |
| Thread Tools | |
| Display Modes | |
|
|