Hi, I'm did some work for a NGO, setting up a small wireless network with SAMBA server. The office has 6 PCs, 4 WinXP and 2 Win98SE. Now I have two problems: 1) Win98SE connects to SAMBA but it takes ages to open folder or put the file on the server. The same thing in XP works instantly. Why is that? 2) They want to enable that users from other cities have access to the server. It's a DSL connection and, as I said, with Wireless Access Point. What is the best way to make that possible: with SAMBA (I know there is some security issues with SAMBA shares over internet), with FTP access or something else? What ports I have to let pass through DSL router in case of SAMBA? Any comments are appreciated, Thanks, Dejan
On Tue, 2003-05-20 at 14:50, Dejan B wrote:
Hi,
I'm did some work for a NGO, setting up a small wireless network with SAMBA server. The office has 6 PCs, 4 WinXP and 2 Win98SE. Now I have two problems:
1) Win98SE connects to SAMBA but it takes ages to open folder or put the file on the server. The same thing in XP works instantly. Why is that?
2) They want to enable that users from other cities have access to the server. It's a DSL connection and, as I said, with Wireless Access Point. What is the best way to make that possible: with SAMBA (I know there is some security issues with SAMBA shares over internet), with FTP access or something else? What ports I have to let pass through DSL router in case of SAMBA?
Any comments are appreciated, Thanks, Dejan
NO NO NO NO NO, do not share this out to the internet. Use a VPN tunnel to share to other offices.
Thaks for the commment. I don't have any expirience with VPN, only a bit of theory. To my knoledge, the client will have to be configured also to access this network if I make it with VPN...problem is, there is no one to configure clients in other parts of the country... Thaks, Dejan Ken Schneider wrote:
On Tue, 2003-05-20 at 14:50, Dejan B wrote:
Hi,
I'm did some work for a NGO, setting up a small wireless network with SAMBA server. The office has 6 PCs, 4 WinXP and 2 Win98SE. Now I have two problems:
1) Win98SE connects to SAMBA but it takes ages to open folder or put the file on the server. The same thing in XP works instantly. Why is that?
2) They want to enable that users from other cities have access to the server. It's a DSL connection and, as I said, with Wireless Access Point. What is the best way to make that possible: with SAMBA (I know there is some security issues with SAMBA shares over internet), with FTP access or something else? What ports I have to let pass through DSL router in case of SAMBA?
Any comments are appreciated, Thanks, Dejan
NO NO NO NO NO, do not share this out to the internet. Use a VPN tunnel to share to other offices.
On Tue, 2003-05-20 at 14:34, Dejan B wrote:
NO NO NO NO NO, do not share this out to the internet. Use a VPN tunnel to share to other offices.
Thaks for the commment. I don't have any expirience with VPN, only a bit of theory. To my knoledge, the client will have to be configured also to access this network if I make it with VPN...problem is, there is no one to configure clients in other parts of the country...
I just want to weigh in on this in agreement with the idea that you ought to be using a VPN. Specifically, you should be looking at PoPToP. It's even included in the distro. Setting it up is primarily a function of configuring the server; the client side is very simple. If you're doing this job professionally, you ought to learn to get comfortable with writing technical documentation. Simply make an instruction booklet with the exact steps, including sample screenshots, of how to configure the clients, and send that to the remote users for _them_ to perform. Regards, dk
Dejan B wrote:
Hi,
I'm did some work for a NGO, setting up a small wireless network with SAMBA server. The office has 6 PCs, 4 WinXP and 2 Win98SE. Now I have two problems:
1) Win98SE connects to SAMBA but it takes ages to open folder or put the file on the server. The same thing in XP works instantly. Why is that?
2) They want to enable that users from other cities have access to the server. It's a DSL connection and, as I said, with Wireless Access Point. What is the best way to make that possible: with SAMBA (I know there is some security issues with SAMBA shares over internet), with FTP access or something else? What ports I have to let pass through DSL router in case of SAMBA?
Any comments are appreciated, Thanks, Dejan
There are several possibilities. FTP is possible but doesn't allow secure access. sftp is just as easy to set up but is secure - only I don't know of any good sftp clients in Windows. The following are possible. 1. Use winscp from http://www.winscp.org/ as an scp client. It looks like Windows Explorer and allows secure remote transfer over ssh. You shouldn't need any special setup on SuSE to get this to work. 2. Make local mirrors using rsync/intersync and put samba on the other end. This is a lot harder, but I think it can be done reliably. -- JDL Non enim propter gloriam, diuicias aut honores pugnamus set propter libertatem solummodo quam Nemo bonus nisi simul cum vita amittit.
Thanks John. I think this will do it! John Lamb wrote:
Dejan B wrote:
Hi,
I'm did some work for a NGO, setting up a small wireless network with SAMBA server. The office has 6 PCs, 4 WinXP and 2 Win98SE. Now I have two problems:
1) Win98SE connects to SAMBA but it takes ages to open folder or put the file on the server. The same thing in XP works instantly. Why is that?
2) They want to enable that users from other cities have access to the server. It's a DSL connection and, as I said, with Wireless Access Point. What is the best way to make that possible: with SAMBA (I know there is some security issues with SAMBA shares over internet), with FTP access or something else? What ports I have to let pass through DSL router in case of SAMBA?
Any comments are appreciated, Thanks, Dejan
There are several possibilities. FTP is possible but doesn't allow secure access. sftp is just as easy to set up but is secure - only I don't know of any good sftp clients in Windows. The following are possible.
1. Use winscp from http://www.winscp.org/ as an scp client. It looks like Windows Explorer and allows secure remote transfer over ssh. You shouldn't need any special setup on SuSE to get this to work.
2. Make local mirrors using rsync/intersync and put samba on the other end. This is a lot harder, but I think it can be done reliably.
participants (4)
-
David Krider -
Dejan B -
John Lamb -
Ken Schneider