Hello - I have installed the latest version of SUSE Linux as a clean install; the original version (was much older from about 2002) could see the same Windows Workgroup, connect to Win shares and vice-versa.
WIth the new version, I can see the LINUX server appear in my WORKGROUP, but when I try to connect to the shares which I have setup - it asks for user/pass. I try every combination from the 'root' password to an admin account password. I turned off the LINUX (and Windows) firewalls. The Shares (on LINUX) are setup in YAST. One XP computer and connect to the Vista computer using shares (and vice-versa); but, when the LINUX/Samba server enters the picture, LINUX reports "Timeout on WORKGROUP" and cannot see the Windows Shares. Again, Windows computers can see the LINUX Shares, but just cannot connect to them regardless of the password/name combos I have tried. The LINUX computer can browse Internet, etc and the router sees the IP/Mac address of the LINUX box. THANKS in advance.
2007-02-11 04:01:17 · 3 answers · asked by Chris C 3 in Computers & Internet ➔ Computer Networking
IP is setup correctly - as I mentioned, I can browse the web on the LINUX system and all Windows computers can see (browse) the LINUX shares; they just cannot connect to them and vice-versa.
2007-02-11 05:05:42 · update #1
Did you create an account in samba with smbpasswd? ;)
2007-02-17 08:18:15 · answer #1 · answered by computercornerplus 2 · 0⤊ 0⤋
computers are a piece -- for this reason they have been designed with a purpose in strategies. What purpose are you making plans on utilising this computing gadget for? which will answer your question as to it fairly is greater efficient. domicile windows 2003 could be utilized as a pc working device, besides the undeniable fact that it would be greater intense priced and characteristic compatibility matters domicile windows XP isn't a solid SERVER OS via fact it would not help all the centers/roles that Server 2003 does and would purely settle for 5 simultaneous connections to it. So as an occasion, in case you shared a folder, purely 5 customers would desire to get admission to it on a similar time. domicile windows XP won't be able to be area Controller DHCP server WDS server WSUS server VPN server DNS server to call some additionally domicile windows XP domicile won't be able to be a member of an internet site. you may play video games on domicile windows 2003 and set up DirectX and so on. -- yet you would be able to run into problems with some drivers/video games throwing up an errors message indicating that they do no longer help that OS. some domicile anti-virus classes won't set up on domicile windows Server 2003 and could require you to purchase their "employer" version As for the device standards -- they're easily a similar. domicile windows Server 2003 can run on some SLOWER machines then XP, yet no longer nicely. So in case you have an previous computing gadget - possibly 1GHz and 256MB RAM AND all you go with to do is get admission to the internet from it.. then domicile windows Server 2003 could be greater efficient from a hardware attitude, yet from a value attitude.. it is going to value you greater. yet in any different case, if the computing gadget can run XP, it could run 2003 no longer unavoidably any different way around. As for the basically released domicile windows Server 2008 -- assume if the laptop can run VISTA, then it could run Server 2008.
2016-11-03 03:49:06 · answer #2 · answered by Anonymous · 0⤊ 0⤋
just verify that you are mapping to the correct shared folder with the proper path and username and password.
also, make sure your using the right protocol, typically, TCP/IP
2007-02-11 04:06:36 · answer #3 · answered by Dee k 2 · 0⤊ 0⤋