Hot Downloads

Welcome, Guest
Username: Password: Remember me

TOPIC: Windows Server 2003

Windows Server 2003 11 years 7 months ago #8055

  • Lindows
  • Lindows's Avatar
  • Offline
  • Senior Member
  • Posts: 246
  • Karma: 0
Hi All,

i have windows Server 2003 and i wanted to create a filesharing server. im behind a router and a friend of mines told me since NAT is enabled i would a have to do some port forwarding. i dic some research on it, but they were no help. Can anyone guide me and the right directiion.

thank You!
The administrator has disabled public write access.

Re: Windows Server 2003 11 years 7 months ago #8056

  • DaLight
  • DaLight's Avatar
  • Offline
  • Honored Member
  • Posts: 1302
  • Karma: 1
By file sharing, do you mean a server that provides files for download only (like an FTP server), a network file server, or a Kazaa-type file sharing PC?

The reason I ask is that some of the above are not suitable for use over the internet without additional security. Also depending on which of the above you wish to implement, you will need to forward different ports.
The administrator has disabled public write access.

Re: Windows Server 2003 11 years 7 months ago #8058

  • Chris
  • Chris's Avatar
  • Offline
  • Administrator
  • Posts: 1446
  • Thank you received: 13
  • Karma: 8
If I understood Lindows correctly, he is talking about the common file sharing known to us in a LAN environment.

While this is possible, you should be aware of the tremendous overhead involved when transferring files using netbios over tcp/ip (port 139). The overhead is so great that a 100Kb file could take you a total of 350 or more kilobytes to download!

I've seen this problem when connecting to my company's VPN and accessing files via the network - it is highly recommended not to take this approach. You would be better off offering a ftp service as this would prove much faster and valuable.

Cheers,
Chris Partsenidis.
Founder & Editor-in-Chief
www.Firewall.cx
The administrator has disabled public write access.

Re: Windows Server 2003 11 years 7 months ago #8065

  • sahirh
  • sahirh's Avatar
  • Offline
  • Honored Member
  • Posts: 1700
  • Karma: 0
Plus opening up ports 139 / 445 to the external world can be a recipe for disaster... definetely not something you want to do...

Even if the worms don't manage to infect, you'll be getting hit by connections like crazy... not to mention the fact that some script kiddie or the other will definetely be running an SMB bruteforcer out there.

go with SFTP.


Cheers,
Sahir Hidayatullah.
Firewall.cx Staff - Associate Editor & Security Advisor
tftfotw.blogspot.com
The administrator has disabled public write access.

SFTP 11 years 7 months ago #8074

  • Lindows
  • Lindows's Avatar
  • Offline
  • Senior Member
  • Posts: 246
  • Karma: 0
Hey Guys,

Thats for the feed back. I guess i should consider a VLAN connection, or the SFTP. They seem more secure. I just wanted to desinate a computer on my network that some of my friends can access to get files.

Lindows
The administrator has disabled public write access.
Time to create page: 0.082 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup