Re: what Ports are used to map a remote drive



Security is most important. We do IP Qualify incoming traffic; only traffic
arriving in production from a specific IP can access exposed resources.
What we wanted to do; was again IP qualify incoming traffic, and port
forward to our specific server and allow a specific machine in corporate to
have mapped drive to a specific server in production. We don't know what
ports are needed to allow the internal corporate machine to map that
production machine.

A VPN would exceed the current needs, and Remote Desktop exceeds the current
needs also. We don't want this internal corporate user to have full access
to the subnet which the production server resides in.


"Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx> wrote in message
news:125i4hufcs1e543@xxxxxxxxxxxxxxxxxxxxx
Don't do it! Not that way. You need to set up a VPN. I suppose a firewall
that only allows the specific ports to be opened from a specific IP
address would be a bit safer, but you can set up a VPN by opening port
1723. Any Windows 2000pro or XPpro or 2K/2K3 server can accept a VPN.

...kurt

"Tom Celica" <Tom@xxxxxxxxxxxxx> wrote in message
news:Wd46g.81292$dW3.43892@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We want to map a remote drive in our production network from our
corporate network. The Network Admin asked me what ports do I need to be
opened between the two sites. The drive at the remote site is a Windows
2000 Server NTFS formated drive on a stand alone server. The Client is
also a windows machine either XP or Win2k or Win2003. I'm pretty sure
that some authentication will occur when the remote drive is mapped. We
will probably execute a commande like this: net use r:
\\remote.machine.com\c$ password /user:administrator@xxxxxxxxxxxxxxxxxx

What ports on our firewall need to be opened so we can map a remote
windows drive ?

thanks
-tom





.



Relevant Pages

  • Re: LISTENING, ESTABLISHED, CLOSE_WAIT TCP Ports & UDP Ports?
    ... properties of a process and it will show you what tcp/ip ports and services ... Beyond that I suggest you read the Windows 2003 Server Security Guide to see ...
    (microsoft.public.windows.server.security)
  • Re: Virtual Private Network - Beware its a Hackers Secret
    ... I don't think I've ever been on a Windows platform. ... > checked for open ports. ... since hackers love to install a bunch of their crap here. ... > Server, NNTP Server, SMTP Server, Web Server, SQL Server and a Virtual ...
    (comp.security.firewalls)
  • Re: Virtual Private Network - Beware its a Hackers Secret
    ... I don't think I've ever been on a Windows platform. ... > checked for open ports. ... since hackers love to install a bunch of their crap here. ... > Server, NNTP Server, SMTP Server, Web Server, SQL Server and a Virtual ...
    (alt.computer.security)
  • Re: Virtual Private Network - Beware its a Hackers Secret
    ... I don't think I've ever been on a Windows platform. ... > checked for open ports. ... since hackers love to install a bunch of their crap here. ... > Server, NNTP Server, SMTP Server, Web Server, SQL Server and a Virtual ...
    (microsoft.public.security)
  • Re: Best desktop OS for VS 2005
    ... utterly stupid and breaks every rule of client/server computing. ... We're talking about putting a server OS on a development computer. ... Windows XP, I'm not surprised. ... nobody said anything about doing development work on "a production ...
    (microsoft.public.vsnet.general)