Re: [Samba] ports
On Thu, May 09, 2013 at 10:02:23AM -0700, Jessica Guynn wrote: > Is there a parameter for smb config for incoming connections to originate > from ports greater than 1024 (insecure ports)? smbd doesn't care what port number the incoming connection is arriving from. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] ports
Is there a parameter for smb config for incoming connections to originate from ports greater than 1024 (insecure ports)? If not, can I set the smb ports like this "smb ports = 1033" in the global section? Thanks guys! -Jessica -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba ports
On Tue, 2012-10-09 at 19:06 -0300, Marcio Oli wrote: > Anybody could help me with this entries in my machines logs: > > [2012/10/09 14:59:33.092831, 0] lib/util_sock.c:474(read_fd_with_timeout) > [2012/10/09 14:59:33.093013, 0] > lib/util_sock.c:1441(get_peer_addr_internal) > getpeername failed. Error was Ponto final de transporte não está > conectado (some logs in portuguese, so the translation is > so so: Error was transport endpoint is not connected) > read_fd_with_timeout: client 0.0.0.0 read error = Conexão fechada pela > outra ponta.( ...: connection closed by other peer) > > Why this appears frequently? > > I had already heard that this is a problem with a connection about the > windows clients. Is this true? > In my smb.conf: > smb ports = 139 445 We have since made this message less prominent. The windows client will connect to both ports, and then drop one connection. It is harmless. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba ports
Anybody could help me with this entries in my machines logs: [2012/10/09 14:59:33.092831, 0] lib/util_sock.c:474(read_fd_with_timeout) [2012/10/09 14:59:33.093013, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Ponto final de transporte não está conectado (some logs in portuguese, so the translation is so so: Error was transport endpoint is not connected) read_fd_with_timeout: client 0.0.0.0 read error = Conexão fechada pela outra ponta.( ...: connection closed by other peer) Why this appears frequently? I had already heard that this is a problem with a connection about the windows clients. Is this true? In my smb.conf: smb ports = 139 445 Thanks, -- Marcio Oliveira. "Tudo concorre para o bem daqueles que amam à Deus." (Rom 8,28) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] I am so frustrated - Samba ports not opening and no error message
Am Freitag 05 Juni 2009 23:40:20 schrieb Matt Burkhardt: > Okay - I've been plugging away and it got to the point that running > smbclient was returning information about an Alfresco install that I > never used, so I went ahead and deleted everything I could find on my > machine that said "alfresco". I then removed samba using apt-get from > the machine by typing > > apt-get remove --purge samba > > I deleted the /etc/samba directory and re-installed samba. > > So now I've made sure that DHCP, DNS and OpenLDAP are now working > correctly and I started to reconfigure Samba. I start it up and I look > at the log.smbd and log.nmbd files, don't see a single error message and > when I run nmap - there's nothing listening on the ports that Samba is > supposed to be using. I have no firewall set up and nothing between me > and the server. Here's showing that the daemons are running: > > ps -e | grep mb > 6984 ?00:00:00 nmbd > 6986 ?00:00:00 smbd > > Here's the results from nmap > > nmap ubuntu > Is "ubuntu" equal to localhost or did you nmap remotely? > Starting Nmap 4.53 ( http://insecure.org ) at 2009-06-05 17:34 EDT > Interesting ports on 192.168.1.100: > Not shown: 1697 closed ports > PORT STATE SERVICE > 22/tcpopen ssh > 53/tcpopen domain > 80/tcpopen http > 81/tcpopen hosts2-ns > 82/tcpopen xfer > 83/tcpopen mit-ml-dev > 111/tcp open rpcbind > 389/tcp open ldap > 443/tcp open https > 631/tcp open ipp > 901/tcp open samba-swat That's the only samba-related port I can find open ... You may try https://ubuntu:901 or uninstall the samba-swat package. > On a side note - I can't stop samba by running > > sudo /etc/init.d/samba stop > > It kills the nmbd daemon but not the smbd daemon > Can you strace -p and look where it hangs? Interestingly, the attached logfiles don't show anything special. You might as well try to specify (man smb.conf) a "interfaces" global statement? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] I am so frustrated - Samba ports not opening and no error message
On Fri, Jun 05, 2009 at 05:40:20PM -0400, Matt Burkhardt wrote: > Okay - I've been plugging away and it got to the point that running > smbclient was returning information about an Alfresco install that I > never used, so I went ahead and deleted everything I could find on my > machine that said "alfresco". I then removed samba using apt-get from > the machine by typing > > apt-get remove --purge samba > > I deleted the /etc/samba directory and re-installed samba. > > So now I've made sure that DHCP, DNS and OpenLDAP are now working > correctly and I started to reconfigure Samba. I start it up and I look > at the log.smbd and log.nmbd files, don't see a single error message and > when I run nmap - there's nothing listening on the ports that Samba is > supposed to be using. I have no firewall set up and nothing between me > and the server. Here's showing that the daemons are running: > > ps -e | grep mb > 6984 ?00:00:00 nmbd > 6986 ?00:00:00 smbd > > Here's the results from nmap > > nmap ubuntu > > Starting Nmap 4.53 ( http://insecure.org ) at 2009-06-05 17:34 EDT > Interesting ports on 192.168.1.100: > Not shown: 1697 closed ports > PORT STATE SERVICE > 22/tcpopen ssh > 53/tcpopen domain > 80/tcpopen http > 81/tcpopen hosts2-ns > 82/tcpopen xfer > 83/tcpopen mit-ml-dev > 111/tcp open rpcbind > 389/tcp open ldap > 443/tcp open https > 631/tcp open ipp > 901/tcp open samba-swat > 3306/tcp open mysql > 5001/tcp open commplex-link > 5432/tcp open postgres > 8009/tcp open ajp13 > 8080/tcp open http-proxy > 1/tcp open snet-sensor-mgmt This ports list shows smbd is not binding to the external ports. smbd uses TCP 139 & 445. nmbd uses udp 137 and 138. Jeremy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] I am so frustrated - Samba ports not opening and no error message
Okay - I've been plugging away and it got to the point that running smbclient was returning information about an Alfresco install that I never used, so I went ahead and deleted everything I could find on my machine that said "alfresco". I then removed samba using apt-get from the machine by typing apt-get remove --purge samba I deleted the /etc/samba directory and re-installed samba. So now I've made sure that DHCP, DNS and OpenLDAP are now working correctly and I started to reconfigure Samba. I start it up and I look at the log.smbd and log.nmbd files, don't see a single error message and when I run nmap - there's nothing listening on the ports that Samba is supposed to be using. I have no firewall set up and nothing between me and the server. Here's showing that the daemons are running: ps -e | grep mb 6984 ?00:00:00 nmbd 6986 ?00:00:00 smbd Here's the results from nmap nmap ubuntu Starting Nmap 4.53 ( http://insecure.org ) at 2009-06-05 17:34 EDT Interesting ports on 192.168.1.100: Not shown: 1697 closed ports PORT STATE SERVICE 22/tcpopen ssh 53/tcpopen domain 80/tcpopen http 81/tcpopen hosts2-ns 82/tcpopen xfer 83/tcpopen mit-ml-dev 111/tcp open rpcbind 389/tcp open ldap 443/tcp open https 631/tcp open ipp 901/tcp open samba-swat 3306/tcp open mysql 5001/tcp open commplex-link 5432/tcp open postgres 8009/tcp open ajp13 8080/tcp open http-proxy 1/tcp open snet-sensor-mgmt Nmap done: 1 IP address (1 host up) scanned in 0.151 seconds I have attached the log.smbd, log.nmbd and smb.conf files. Any ideas? I can't logon - just says Connection refused. On a side note - I can't stop samba by running sudo /etc/init.d/samba stop It kills the nmbd daemon but not the smbd daemon Thanks! -- Matt Burkhardt, M.Sci. Technology Management m...@imparisystems.com (301) 682-7901 502 Fairview Avenue Frederick, MD 21701 http://www.imparisystems.com [2009/06/05 17:33:17, 0] nmbd/nmbd.c:main(721) Netbios nameserver version 3.0.28a started. Copyright Andrew Tridgell and the Samba Team 1992-2008 [2009/06/05 17:33:17, 3] nmbd/nmbd.c:reload_nmbd_services(298) services not loaded [2009/06/05 17:33:17, 2] nmbd/nmbd.c:main(745) Becoming a daemon. [2009/06/05 17:33:17, 2] lib/tallocmsg.c:register_msg_pool_usage(105) Registered MSG_REQ_POOL_USAGE [2009/06/05 17:33:17, 2] lib/dmallocmsg.c:register_dmalloc_msgs(75) Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED [2009/06/05 17:33:17, 3] nmbd/nmbd.c:main(783) Opening sockets 137 [2009/06/05 17:33:17, 3] nmbd/nmbd.c:open_sockets(639) open_sockets: Broadcast sockets opened. [2009/06/05 17:33:17, 2] lib/interface.c:add_interface(81) added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0 [2009/06/05 17:33:17, 2] nmbd/nmbd_subnetdb.c:make_subnet(144) making subnet name:192.168.1.100 Broadcast address:192.168.1.255 Subnet mask:255.255.255.0 [2009/06/05 17:33:17, 2] nmbd/nmbd_subnetdb.c:make_subnet(144) making subnet name:UNICAST_SUBNET Broadcast address:192.168.1.100 Subnet mask:192.168.1.100 [2009/06/05 17:33:17, 2] nmbd/nmbd_subnetdb.c:make_subnet(144) making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0 [2009/06/05 17:33:17, 2] nmbd/nmbd_subnetdb.c:make_subnet(144) making subnet name:WINS_SERVER_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0 [2009/06/05 17:33:17, 2] nmbd/nmbd_lmhosts.c:load_lmhosts_file(41) load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory [2009/06/05 17:33:17, 3] nmbd/nmbd.c:main(802) Loaded hosts file /etc/samba/lmhosts [2009/06/05 17:33:17, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(247) add_name_to_subnet: Added netbios name *<00> with first IP 192.168.1.100 ttl=0 nb_flags=60 to subnet WINS_SERVER_SUBNET [2009/06/05 17:33:17, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(247) add_name_to_subnet: Added netbios name *<20> with first IP 192.168.1.100 ttl=0 nb_flags=60 to subnet WINS_SERVER_SUBNET [2009/06/05 17:33:17, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(247) add_name_to_subnet: Added netbios name __SAMBA__<20> with first IP 192.168.1.100 ttl=0 nb_flags=60 to subnet WINS_SERVER_SUBNET [2009/06/05 17:33:17, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(247) add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 192.168.1.100 ttl=0 nb_flags=60 to subnet WINS_SERVER_SUBNET [2009/06/05 17:33:17, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(247) add_name_to_subnet: Added netbios name UBUNTU<03> with first IP 192.168.1.100 ttl=259053 nb_flags=66 to subnet WINS_SERVER_SUBNET [2009/06/05 17:33:17, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(247) add_name_to_subnet: Added netbios name UBUNTU<20> with first IP 192.168.1.100 ttl=259053 nb_flags=66 to subnet WINS_SERVER_SUBNET [2009/06/05 17:33:17, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(247) add_name_to_subnet: Added netbios name WORKGRO
[Samba] Disappearing samba ports
I have new install of Debian, primarily "testing" with some "stable". The kernel is 2.6.21-2. I am having problems with a Samba (3.0.25b-1+b1, 3.0.25b-1) install. smb.conf is from a template I have used several times previously (including 3.0.25b) with no problems. From Windows Explorer, the shares will be slow to appear, with folders and files in the right pane appearing and disappearing. After some time, the shares will become completely inaccessible. In an attempt to correct, I restarted both Samba processes, which not only did not help, but made worse. The log files gave messages suggesting firewall problems, but there is no firewall. NMAP showed both samba ports closed, but open again after a reboot. A restart of Samba causes the ports to close again leading to the error messages mentioned previously. Samba is set up as a standalone server in a workgroup with security = user, passdb backend = tdbsam. After the initial install, I was able to upload printer drivers and did not notice any speed problems. Changes to the system since the initial Samba install are the latest hplip (2.7.7) from sourceforge and an iptables update from Debian. I cannot determine from the logs if the problem is from Samba, such as tdb corruption, or something else in the system. I would think that ports should not spontaneously close. I'm hoping someone can give me their best guess as to where to look next. Thanks, Dale -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Ports
Shaun Marolf wrote: Okay my smb.conf file is correct. Firewall is configured correctly to allow Samba on local network. smbd and nmbd are running. Her computer still cannot connect to my printer share. I read my Samba version wrong its actually 3.0.23a-1.fc5.1, here is my smb.conf: [global] workgroup = HOME realm = SHAUN server string = Samba Server security = SHARE encrypt passwords = No log file = /var/log/samba/%m.log max log size = 50 dns proxy = No wins support = Yes ldap ssl = no admin users = shaun read list = shaun write list = shaun printer admin = shaun cups options = raw [printers] comment = All Printers path = /usr/spool/samba guest ok = Yes printable = Yes browseable = No [LaserJet_4] comment = HP LaserJet 4/4M path = /usr/spool/samba read only = No guest ok = Yes printable = Yes printer name = LaserJet_4 oplocks = No share modes = No I am using Fedora Core 5 She has Windows XP Media Center Edition. I cannot see her computer at all when I try to browse with smb4k or with my file manager. She cannot can see my computer if I scan from her station but she cannot connect to me. I ran a scan on SMB ports from her and they show as open so she should see my printer but doesn't. My firewall is reporting the attempt of ports like 35578 attempting to make an inbound connection from her. Did MS change things again or is there something else? --Shaun I had once some problems regarding SMB connections and firewalls; according to Microsoft the ports needed to make this kind of connections should be 135/UDP, 137/UDP, 138/UDP, 139/TCP and 445/TCP, but if I open these ports using iptables and block anything else, the connections are not possible. I tried all the port/protocol posible combinations and could not make it... Good luck. -- Miguel Da Silva. Servicio de Informatica. Facultad de Ciencias. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Ports
Okay my smb.conf file is correct. Firewall is configured correctly to allow Samba on local network. smbd and nmbd are running. Her computer still cannot connect to my printer share. I read my Samba version wrong its actually 3.0.23a-1.fc5.1, here is my smb.conf: [global] workgroup = HOME realm = SHAUN server string = Samba Server security = SHARE encrypt passwords = No log file = /var/log/samba/%m.log max log size = 50 dns proxy = No wins support = Yes ldap ssl = no admin users = shaun read list = shaun write list = shaun printer admin = shaun cups options = raw [printers] comment = All Printers path = /usr/spool/samba guest ok = Yes printable = Yes browseable = No [LaserJet_4] comment = HP LaserJet 4/4M path = /usr/spool/samba read only = No guest ok = Yes printable = Yes printer name = LaserJet_4 oplocks = No share modes = No I am using Fedora Core 5 She has Windows XP Media Center Edition. I cannot see her computer at all when I try to browse with smb4k or with my file manager. She cannot can see my computer if I scan from her station but she cannot connect to me. I ran a scan on SMB ports from her and they show as open so she should see my printer but doesn't. My firewall is reporting the attempt of ports like 35578 attempting to make an inbound connection from her. Did MS change things again or is there something else? --Shaun -- It isn't about it being free. Rather its about the freedom it brings. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Ports for printing
The output of: cat /etc/services | grep -i bios netbios-ns 137/tcp # NETBIOS Name Service netbios-ns 137/udp netbios-dgm 138/tcp # NETBIOS Datagram Service netbios-dgm 138/udp netbios-ssn 139/tcp # NETBIOS session service netbios-ssn 139/udp You don't need all of these, some are essentially non-functional and present no security hazard. To see which ports your server is listening on: netstat -apn | grep -i smbd tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 2250/smbd If smbd is started by xinitd or initd, you won't see the output above. Then, xinitd will be watching that port. nmbd listens on ports 137 and 138, udp. I do not know what a Datagram service is, BTW. Joel On Tue, May 27, 2003 at 10:21:31AM +0200, Jan Madsen wrote: > Hallo > I'm using samba 2.2.8a rpm packet on a redhat 9.0 > On the same machine I use iptables with standard policies with DROP > > With ports do I need to open for printing on from my windows pc to work > > Best Regards > Jan madsen > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Ports Recommended?
Hi All, I finally got a completely new box (Multiple Domains Thread from last month) and have just done a fresh FreeBSD 4.7 install. I used to use a source tarball, but am wondering if there's any reason to not use the ports tree. TIA Steve -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Ports that Samba Uses
Hi Walter, 139/TCP - Netbios-ssn for samba, 901/TCP - Swat - (If you are using SWAT). Good Day, Jason Stewart At 11:32 AM 6/3/2002 -0700, Walter Weiss wrote: >Is there a list somewhere of every port a linux box running redhat 7.1 >uses or might use for the samba services? I need to set up my router to >be able to access samba from another port but I"m not sure which ones to >forward. > >THanks, > >Walter Weiss Jason Stewart Systems Administrator/Programmer Right to Life of Michigan Tel: (616)532-2300 Fax: (616)532-3461 To find out where Michigan Gubernatorial Candidate Jennifer Granholm really stands, please visit http://www.granholmgarble.com/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Ports that Samba Uses
Walter, # grep netbios /etc/services netbios-ns 137/tcp # NETBIOS Name Service netbios-ns 137/udp netbios-dgm 138/tcp # NETBIOS Datagram Service netbios-dgm 138/udp netbios-ssn 139/tcp # NETBIOS session service netbios-ssn 139/udp Ingmar. On Monday 03 June 2002 02:32 pm, Walter Weiss wrote: > Is there a list somewhere of every port a linux box running redhat 7.1 uses > or might use for the samba services? I need to set up my router to be able > to access samba from another port but I"m not sure which ones to forward. > > THanks, > > Walter Weiss -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Ports that Samba Uses
Is there a list somewhere of every port a linux box running redhat 7.1 uses or might use for the samba services? I need to set up my router to be able to access samba from another port but I"m not sure which ones to forward. THanks, Walter Weiss
Re: [Samba] samba ports blocked by isp
Win2k and WinXP will automatically try to connect to port 445 in addition to port 139. Earlier versions of Windows like NT, ME, 9x aren't able to use port 445 at all. To use port 445 with smbd, you need to put an entry in /etc/inetd.conf that looks liks this: microsoft-ds stream tcp nowait root /usr/local/samba/sbin/smbd smbd Make sure the path is right, and *don't* use the -D flag! Also, if you don't have microsoft-ds in your /etc/services, you'll need to add it as tcp/445. If you don't have inetd, you probably have some replacement like xinetd or rlinetd, and you need to figure those out yourself. :-) -Nathan On Fri, Apr 26, 2002 at 07:48:09AM -0500, Barry Smoke wrote: > is there something special I need to make this work on both ends > or should this work by default? > > On Fri, 2002-04-26 at 07:02, Nathan Lutchansky wrote: > > On Wed, Apr 24, 2002 at 04:55:56PM -0500, Gerald Carter wrote: > > > On Wed, 24 Apr 2002, Barry Smoke wrote: > > > > > > > Is it possible to map a drive to a samba share over the internet, > > > > through an isp that blocks the samba ports... I know with samba, I can > > > > specify a port, but what about a windows client? Can I change what port > > > > a windows machine looks to for samba/smb for a particular share only? > > > > > > You really don;t want to do this. It is **so** insecure. > > > > Why is that? As long as you're using encrypted passwords and you're not > > transferring sensitive data, what is insecure about it? > > > > > Setup a VPN it is it necessary to share files using CIFS > > > across the 'Net. > > > > If the ISP only blocks ports 137-139, connecting on port 445 would work, > > provided the client is a Win2k or WinXP box. Works fine on Road Runner > > here. -Nathan > > > > -- > > +---+-++ > > | Nathan Lutchansky | [EMAIL PROTECTED] | Lithium Technologies | > > +--+ > > | I dread success. To have succeeded is to have finished one's | > > | business on earth... I like a state of continual becoming, | > > | with a goal in front and not behind. - George Bernard Shaw | > > +--+ > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba -- +---+-++ | Nathan Lutchansky | [EMAIL PROTECTED] | Lithium Technologies | +--+ | I dread success. To have succeeded is to have finished one's | | business on earth... I like a state of continual becoming, | | with a goal in front and not behind. - George Bernard Shaw | +--+ msg01232/pgp0.pgp Description: PGP signature
Re: [Samba] samba ports blocked by isp
is there something special I need to make this work on both ends or should this work by default? On Fri, 2002-04-26 at 07:02, Nathan Lutchansky wrote: > On Wed, Apr 24, 2002 at 04:55:56PM -0500, Gerald Carter wrote: > > On Wed, 24 Apr 2002, Barry Smoke wrote: > > > > > Is it possible to map a drive to a samba share over the internet, > > > through an isp that blocks the samba ports... I know with samba, I can > > > specify a port, but what about a windows client? Can I change what port > > > a windows machine looks to for samba/smb for a particular share only? > > > > You really don;t want to do this. It is **so** insecure. > > Why is that? As long as you're using encrypted passwords and you're not > transferring sensitive data, what is insecure about it? > > > Setup a VPN it is it necessary to share files using CIFS > > across the 'Net. > > If the ISP only blocks ports 137-139, connecting on port 445 would work, > provided the client is a Win2k or WinXP box. Works fine on Road Runner > here. -Nathan > > -- > +---+-++ > | Nathan Lutchansky | [EMAIL PROTECTED] | Lithium Technologies | > +--+ > | I dread success. To have succeeded is to have finished one's | > | business on earth... I like a state of continual becoming, | > | with a goal in front and not behind. - George Bernard Shaw | > +--+ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba ports blocked by isp
On Wed, Apr 24, 2002 at 04:55:56PM -0500, Gerald Carter wrote: > On Wed, 24 Apr 2002, Barry Smoke wrote: > > > Is it possible to map a drive to a samba share over the internet, > > through an isp that blocks the samba ports... I know with samba, I can > > specify a port, but what about a windows client? Can I change what port > > a windows machine looks to for samba/smb for a particular share only? > > You really don;t want to do this. It is **so** insecure. Why is that? As long as you're using encrypted passwords and you're not transferring sensitive data, what is insecure about it? > Setup a VPN it is it necessary to share files using CIFS > across the 'Net. If the ISP only blocks ports 137-139, connecting on port 445 would work, provided the client is a Win2k or WinXP box. Works fine on Road Runner here. -Nathan -- +---+-++ | Nathan Lutchansky | [EMAIL PROTECTED] | Lithium Technologies | +--+ | I dread success. To have succeeded is to have finished one's | | business on earth... I like a state of continual becoming, | | with a goal in front and not behind. - George Bernard Shaw | +--+ msg01224/pgp0.pgp Description: PGP signature
Re: [Samba] samba ports blocked by isp
On Wed, 24 Apr 2002, Barry Smoke wrote: > Is it possible to map a drive to a samba share over the internet, > through an isp that blocks the samba ports... I know with samba, I can > specify a port, but what about a windows client? Can I change what port > a windows machine looks to for samba/smb for a particular share only? You really don;t want to do this. It is **so** insecure. Setup a VPN it is it necessary to share files using CIFS across the 'Net. chau, jerry - Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org --http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba ports blocked by isp
Is it possible to map a drive to a samba share over the internet, through an isp that blocks the samba ports... I know with samba, I can specify a port, but what about a windows client? Can I change what port a windows machine looks to for samba/smb for a particular share only? Barry Smoke Network Administrator Bryant Public Schools -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
