[Samba] XP Home client problems.
Hi, Please ignore this mail if you have already received this mail before. I have been trying for 2 frustrating weeks to get my XP Home machine to talk to the Samba server on my SuSE 9.2 Linux box. Described below is the crux of the problem. When I do an smbclient on the Linux box I can see the Windows machine listed. However, when I do a net view on the Windows XP Home machine I do not see the Samba box. Also, I get a System 1 error on the XP machine if the XP is not the Local Master Browser and, if it is only the XP machine is visible in the output of the net view. I have removed all firewall services, enabled cleartext password in XP and enabled guest access and no encryption in Samba. Also, I have disabled the firewall on the Linux box. I don't know whether this will be of any use in debugging, When I do a net use on the XP box, and monitor the IP flow, I see traffic destined to port 80 on the Linux box from the XP box. I got the setup to work, however, after a reboot of the XP box I am back to the square one. Any help would be greatly appreciated. Thanks, -Venkata. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP Home client problems.
I can't comment on most of your issue, but for this one I do have some advice: I don't know whether this will be of any use in debugging, When I do a net use on the XP box, and monitor the IP flow, I see traffic destined to port 80 on the Linux box from the XP box. I can't remember exactly what the proper term is for this, but it is the webclient service in XP doing that. It can cause some performance problems if not dealt with, so you have two basic options. 1. Disable the webclient service on the XP box. This stops the requests entirely. 2. Set up a web server on the linux box. This provides something that will give an explicit no when the XP machine comes looking for data rather than waiting for a timeout. I usually do this one because it's quicker for me to set up a basic web server than turn off every client in the network. -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP Home client problems.
Thanks for the heads up, we'll be adding net stop webclient to our login scripts. -- John Schmerold Katy Computer Wireless 20 Meramec Station Rd Valley Park MO 63088 636-861-6900 v 775-227-6947 f Paul Gienger wrote: I can't comment on most of your issue, but for this one I do have some advice: I don't know whether this will be of any use in debugging, When I do a net use on the XP box, and monitor the IP flow, I see traffic destined to port 80 on the Linux box from the XP box. I can't remember exactly what the proper term is for this, but it is the webclient service in XP doing that. It can cause some performance problems if not dealt with, so you have two basic options. 1. Disable the webclient service on the XP box. This stops the requests entirely. 2. Set up a web server on the linux box. This provides something that will give an explicit no when the XP machine comes looking for data rather than waiting for a timeout. I usually do this one because it's quicker for me to set up a basic web server than turn off every client in the network. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
