Re: [Samba] Port 139 versus Port 445
Anyone have a sample line from inetd.conf that gets smbd to start on port 445 when smbd is already running on 139 from the samba startup script? I haven't had any luck yet? The following works for me: (sorry abt the line break) microsoft-dsstream tcp nowait root/usr/local/samba/bin/smbd smbd -d 1 Glen Gibb Ridley College -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Port 139 versus Port 445
Just make sure that the /etc/services file has microsoft-ds defined in it. Mine doesn't. Joel On Mon, Nov 04, 2002 at 11:51:54AM +1100, Glen Gibb wrote: Anyone have a sample line from inetd.conf that gets smbd to start on port 445 when smbd is already running on 139 from the samba startup script? I haven't had any luck yet? The following works for me: (sorry abt the line break) microsoft-dsstream tcp nowait root/usr/local/samba/bin/smbd smbd -d 1 Glen Gibb Ridley College -- 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
Re: [Samba] Port 139 versus Port 445
Andrew Bartlett wrote: Joel Hammer wrote: I suspect that you can have two smbd's running. Each one will spawn other daemons as needed, I THINK. Joel You can only have one smbd running as a daemon. You can start others via inetd however. The issue of 139/445 has been addressed in 3.0 by listining on both ports by default. Andrew Bartlett Anyone have a sample line from inetd.conf that gets smbd to start on port 445 when smbd is already running on 139 from the samba startup script? I haven't had any luck yet? Thanks, Jason Joines == -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Port 139 versus Port 445
Jason Joines wrote: I have been running an smbd daemon on port 445 with the -p option but have never been able to start a second daemon. No, you can only have one deamon, but you can run another via inetd. -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Port 139 versus Port 445
Joel Hammer wrote: I suspect that you can have two smbd's running. Each one will spawn other daemons as needed, I THINK. Joel You can only have one smbd running as a daemon. You can start others via inetd however. The issue of 139/445 has been addressed in 3.0 by listining on both ports by default. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Port 139 versus Port 445
Joel Hammer wrote: Just making all this stuff up off the top of my head. I have never done this, but you could try: Running two smbd daemon, each listening to different ports. Redirecting traffic from port 445 to 139 with some firewall rules. I redirect traffic with ipmasqadm, but there are surely others. Running smbd with (x)inetd and have it listen to both ports. Likely, the delay is because the W2K clients are waiting for a reply, and finally timing out on port 445. Why not try something funky like having telnet or apache listen on port 445. Maybe that will tell the client right away to try a different port, like 139. Let us know how this works out, if you try any of this stuff. Joel On Thu, Oct 03, 2002 at 03:04:41PM -0500, Jason Joines wrote: I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba I have been running an smbd daemon on port 445 with the -p option but have never been able to start a second daemon. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Port 139 versus Port 445
I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Port 139 versus Port 445
Just making all this stuff up off the top of my head. I have never done this, but you could try: Running two smbd daemon, each listening to different ports. Redirecting traffic from port 445 to 139 with some firewall rules. I redirect traffic with ipmasqadm, but there are surely others. Running smbd with (x)inetd and have it listen to both ports. Likely, the delay is because the W2K clients are waiting for a reply, and finally timing out on port 445. Why not try something funky like having telnet or apache listen on port 445. Maybe that will tell the client right away to try a different port, like 139. Let us know how this works out, if you try any of this stuff. Joel On Thu, Oct 03, 2002 at 03:04:41PM -0500, Jason Joines wrote: I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind -- 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
Re: [Samba] Port 139 versus Port 445
man smb.conf / -p Joel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Port 139 versus Port 445
am curious and need to configure this and test, any ideas how to make it work, i mean how do start 2 smbd parent process is it port based or something else samba technical group please comment on this if you get chance thanks in advance -Original Message- From: Joel Hammer [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 03, 2002 5:47 PM To: Javid Abdul-AJAVID1; [EMAIL PROTECTED] Subject: Re: [Samba] Port 139 versus Port 445 I suspect that you can have two smbd's running. Each one will spawn other daemons as needed, I THINK. Joel On Thu, Oct 03, 2002 at 05:41:39PM -0500, Javid Abdul-AJAVID1 wrote: I am just curious of running 2 smbds, as i think one parent smbd process runs on 139 and all others are children -Original Message- From: Joel Hammer [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 03, 2002 5:32 PM To: Jason Joines; [EMAIL PROTECTED] Subject: Re: [Samba] Port 139 versus Port 445 Just making all this stuff up off the top of my head. I have never done this, but you could try: Running two smbd daemon, each listening to different ports. Redirecting traffic from port 445 to 139 with some firewall rules. I redirect traffic with ipmasqadm, but there are surely others. Running smbd with (x)inetd and have it listen to both ports. Likely, the delay is because the W2K clients are waiting for a reply, and finally timing out on port 445. Why not try something funky like having telnet or apache listen on port 445. Maybe that will tell the client right away to try a different port, like 139. Let us know how this works out, if you try any of this stuff. Joel On Thu, Oct 03, 2002 at 03:04:41PM -0500, Jason Joines wrote: I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind -- 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 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Port 139 versus Port 445
am curious and need to configure this and test, any ideas how to make it work, i mean how do start 2 smbd parent process is it port based or something else samba technical group please comment on this if you get chance thanks in advance -Original Message- From: Joel Hammer [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 03, 2002 5:47 PM To: Javid Abdul-AJAVID1; [EMAIL PROTECTED] Subject: Re: [Samba] Port 139 versus Port 445 I suspect that you can have two smbd's running. Each one will spawn other daemons as needed, I THINK. Joel On Thu, Oct 03, 2002 at 05:41:39PM -0500, Javid Abdul-AJAVID1 wrote: I am just curious of running 2 smbds, as i think one parent smbd process runs on 139 and all others are children -Original Message- From: Joel Hammer [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 03, 2002 5:32 PM To: Jason Joines; [EMAIL PROTECTED] Subject: Re: [Samba] Port 139 versus Port 445 Just making all this stuff up off the top of my head. I have never done this, but you could try: Running two smbd daemon, each listening to different ports. Redirecting traffic from port 445 to 139 with some firewall rules. I redirect traffic with ipmasqadm, but there are surely others. Running smbd with (x)inetd and have it listen to both ports. Likely, the delay is because the W2K clients are waiting for a reply, and finally timing out on port 445. Why not try something funky like having telnet or apache listen on port 445. Maybe that will tell the client right away to try a different port, like 139. Let us know how this works out, if you try any of this stuff. Joel On Thu, Oct 03, 2002 at 03:04:41PM -0500, Jason Joines wrote: I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind -- 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
