Hi All, This is very urgent, please help me. I have a redhat machine (2.4.9-e.24) which is acting as a samba server (samba - 2.2.7) Everything was going smoothly until we changes the ip address of our windows machines. Now if i try to connect to the server it gives me the error: "windows cannot find '\\titan". Check the spelling and try again." I have tried connecting by using the IP address too but i get the same error. I have added the new ip range in to the smb.conf file. I even tried (for testing purpose) adding the IP address of my windows machine and see if i can connect but i still cant connect. Please advice what i am doing wrong here. I went through the DIAGNOSTICS.txt and failed at test 8 with the error: System error 53 has occurred. The network path was not found. test 9 with the error: System error 59 has occurred. An unexpected network error occurred. test 10 with the error: querying delta on 12.20.194.255 querying delta on 12.20.194.255 name_query failed to find name delta#1d Test 11: cant browse I know this is sone kind of network issue, but i fail to see where... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Fri, 2005-03-18 at 14:26 -0800, indgirl 6 wrote:> Hi All, > This is very urgent, please help me. > > I have a redhat machine (2.4.9-e.24) which is acting as a samba server (samba - 2.2.7) > Everything was going smoothly until we changes the ip address of our windows machines. > Now if i try to connect to the server it gives me the error: > "windows cannot find '\\titan". Check the spelling and try again." > I have tried connecting by using the IP address too but i get the same error. > > I have added the new ip range in to the smb.conf file. I even tried (for testing purpose) adding the IP address of my windows machine and see if i can connect but i still cant connect. Please advice what i am doing wrong here. > > I went through the DIAGNOSTICS.txt and failed at > test 8 with the error: System error 53 has occurred. The network path was not found. > test 9 with the error: System error 59 has occurred. An unexpected network error occurred. > > test 10 with the error: querying delta on 12.20.194.255 > querying delta on 12.20.194.255 > name_query failed to find name delta#1d > > Test 11: cant browse > > I know this is sone kind of network issue, but i fail to see where... > >Can the windows machine even ping the samba server? Ping, traceroute (tracert) tcpdump and or ethereal, as well as the samba logs files might tell you more. Look at things in smaller pieces, make sure the little pieces are doing their work before you look at the assembly of pieces. Ted
Hi, I can ping to the server form windows machine, and vice versa. I can even telnet to server form windows machine. PLease tell me what other check i should do. Ted Kaczmarek <tedkaz@optonline.net> wrote: On Fri, 2005-03-18 at 14:26 -0800, indgirl 6 wrote:> Hi All, > This is very urgent, please help me. > > I have a redhat machine (2.4.9-e.24) which is acting as a samba server (samba - 2.2.7) > Everything was going smoothly until we changes the ip address of our windows machines. > Now if i try to connect to the server it gives me the error: > "windows cannot find '\\titan". Check the spelling and try again." > I have tried connecting by using the IP address too but i get the same error. > > I have added the new ip range in to the smb.conf file. I even tried (for testing purpose) adding the IP address of my windows machine and see if i can connect but i still cant connect. Please advice what i am doing wrong here. > > I went through the DIAGNOSTICS.txt and failed at > test 8 with the error: System error 53 has occurred. The network path was not found. > test 9 with the error: System error 59 has occurred. An unexpected network error occurred. > > test 10 with the error: querying delta on 12.20.194.255 > querying delta on 12.20.194.255 > name_query failed to find name delta#1d > > Test 11: cant browse > > I know this is sone kind of network issue, but i fail to see where... > >Can the windows machine even ping the samba server? Ping, traceroute (tracert) tcpdump and or ethereal, as well as the samba logs files might tell you more. Look at things in smaller pieces, make sure the little pieces are doing their work before you look at the assembly of pieces. Ted --------------------------------- Do you Yahoo!? Yahoo! Small Business - Try our new resources site!
i dont think i am using WINS. I have tried putting the entry of samba server into the locan lmhosts file but of no consequence. Also i restart the smb and nbm service after any change i make, be it on the windows side or linux / samba side. Please advice. TBMDF <support@tbmdf.com> wrote: On Mar 21, 2005, at 6:31 AM, indgirl 6 wrote:> Hi, > > I can ping to the server form windows machine, and vice versa. I can > even telnet to server form windows machine. PLease tell me what other > check i should do. > > >Do you have WINS running? canyou see the server in the Net Hood? try using a hosts/lmhosts file temporarily on the workstations. --------------------------------- Do you Yahoo!? Yahoo! Small Business - Try our new resources site!
Hi All, I just found out that i was not even my backup server could conect to the samba server. The IP of the backup server had changed too. So basically i can login to the samba server from the machines with new IP using ssh etc, and can even ping. but for some reasons some services are not working. I know for sure this is not a firewall issue coz i can see all the traffice passing sucessfully, also all ports on firewall are open (for testing purprose) One thing i notices was that the hosts.allow file did not have the new IP range into it. I have added the new IP range and restarted network services but that did not help either. The hosts.allow file is now as below: portmap: 10.0.0.0/255.255.0.0 , 169.143.0.0/255.255.0.0 , 12.20.194.8 , 12.20.194.7 , 12.20.194.22 lockd: 10.0.0.0/255.255.0.0 , 169.143.0.0/255.255.0.0 , 12.20.194.8 , 12.20.194.7 , 12.20.194.22 rquotad: 10.0.0.0/255.255.0.0 , 169.143.0.0/255.255.0.0 , 12.20.194.8 , 12.20.194.7 , 12.20.194.22 mountd: 10.0.0.0/255.255.0.0 , 169.143.0.0/255.255.0.0 , 12.20.194.8 , 12.20.194.7 , 12.20.194.22 statd: 10.0.0.0/255.255.0.0 , 169.143.0.0/255.255.0.0 , 12.20.194.8 , 12.20.194.7 , 12.20.194.22 nfsd: 10.0.0.0/255.255.0.0 , 169.143.0.0/255.255.0.0 , 12.20.194.8 , 12.20.194.7 , 12.20.194.22 Please advice if i should add anything more to it. Is there any other file in linux that restricts connections based on iprange or something. I am new to linux. Please help. Adam Williams <awilliam@mdah.state.ms.us> wrote: is samba bound to both interfaces? have you tried pinging both and teltenneting to the ports on both? if you still can't connect after that, sounds like smbd isn't running ont he samba server. indgirl 6 wrote:> hi, > > i am not able to telnet to any of these ports from the windows > machine. i get the error, Connecting To 12.20.194.28...Could not open > connection to the host, on port 137: > Connect failed > > my linux machine has 2 9nterface, the IP address og one interface is > 12.20.194.27 and the other one is 12.20.194.28. > > > > */Adam Williams /* wrote: > > did you restart samba after making the changes to smb.conf? Also, try > telnetting to the samba tcp/ip ports. so telnet samba_server_ip 135 > (and 137, 139, 445) see if you can connect to any or go to > www.insecure.org/nmap and run the nmap scanner against the TCP > ports of > the samba server ip and see what it reports to you (do all of this > from > one of the windows pc's unable to connect to the samba server) > > > indgirl 6 wrote: > > >Hi, > > > >I can ping to the server form windows machine, and vice versa. I > can even telnet to server form windows machine. PLease tell me > what other check i should do. > > > > > > > >Ted Kaczmarek wrote: > >On Fri, 2005-03-18 at 14:26 -0800, indgirl 6 wrote: > > > > > >>Hi All, > >>This is very urgent, please help me. > >> > >>I have! a redhat machine (2.4.9-e.24) which is acting as a samba > server (samba - 2.2.7) > >>Everything was going smoothly until we changes the ip address of > our windows machines. > >>Now if i try to connect to the server it gives me the error: > >>"windows cannot find '\\titan". Check the spelling and try again." > >>I have tried connecting by using the IP address too but i get > the same error. > >> > >>I have added the new ip range in to the smb.conf file. I even > tried (for testing purpose) adding the IP address of my windows > machine and see if i can connect but i still cant connect. Please > advice what i am doing wrong here. > >> > >>I went through the DIAGNOSTICS.txt and failed at > >>test 8 with the error: System error 53 has occurred. The network > path was not found. > >>test 9 with the error: System error 59 has occurred. An > unexpected network error occurred. > >> > >>test 10 with the error: querying de! lta on 12.20.194.255 > >>querying delta on 12.20.194.255 > >>name_query failed to find name delta#1d > >> > >>Test 11: cant browse > >> > >>I know this is sone kind of network issue, but i fail to see > where... > >> > >> > >> > >> > >Can the windows machine even ping the samba server? > > > >Ping, traceroute (tracert) tcpdump and or ethereal, as well as > the samba > >logs files might tell you more. > > > > > >Look at things in smaller pieces, make sure the little pieces are > doing > >their work before you look at the assembly of pieces. > > > >Ted > > > > > > > >--------------------------------- > >Do you Yahoo!? > > Yahoo! Small Business - Try our new resources site! > > > > > > > ------------------------------------------------------------------------ > Do you Yahoo!? > Take Yahoo! Mail with you! > > Get it on your mobile phone.--------------------------------- Do you Yahoo!? Yahoo! Small Business - Try our new resources site!