OK - I’ve been trying for at least week to configure the Network. I can talk to any other system in the network, but getting one to talk back to Suse is really taking a toll!!
I’ve got the system on ifup and as far as I can tell, all the numbers are entered for server, gateway, etc. Seems it works fine for all the other systems to talk to one another but Suse remains stubborn.
I can see Suse on the Network listing on the other units and it has no problem connecting to the Internet and so forth, but when I try to connect to another unit it comes back with the login screen saying access is denied. Seems it will not just let me click on a share, enter my user name and password and get into the shares - just comes back saying to try another account.
Any help or at least some direction to go in??? I’m trying to make a transition to Suse from Ubuntu but thos beyond me at this point…
So Texas Jim, a big Howdy from another Texan in Austin. You wrote a lot of words, but not much to help us understand what you are trying to really do.
For openSUSE, we want to know:
openSUSE Version
Desktop Being Used
Number of Linux computers and number or Windows computers.
What kind of Network, local (Private) or commecial
For file sharing between Windows and openSUSE, the normal is to setup Samba. I have a bash script that can do that for you. Have a look at my blog on the subject here:
From Ubuntu to Windows with no issues on Ubuntu - they talk to each other and can talk to everything on line. The only issue is getting Suse to accept ANY connection from a Windows unit, although it can talk to SUSE. I can connect the other units to the SUSE but not the other way 'round. The network is setup for a work network and that’s it. I have no problem connecting with any other system to any other one. The ONLY issue is getting SUSE to accept connection from any other system. Suse is ONE unit I am trying to put online but it refuses to accept any connections from any unit. It seems to be permissions problem but I am mystified that it is the only unit that won’t accept connection fro any other one.
Summary:
Ubuntu to Ubuntu - OK
Ubuntu to Windows - OK
Windows to Ubuntu - OK
Windows to Windows - OK
Suse to Windows/Ubuntu - OK
Windows/Ubuntu to Suse - Fail with no acceptance of Suse to the login
Isn’t this a share permission problem?? If so what’s the magic to get Suse to cooperate???
> Version: 12.3
> Desktop: Gnome
>
> From Ubuntu to Windows with no issues on Ubuntu - they talk to each
> other and can talk to everything on line. The only issue is getting Suse
> to accept ANY connection from a Windows unit, although it can talk to
> SUSE. I can connect the other units to the SUSE but not the other way
> 'round.
Connect to what? SSH? HTTP? FTP? NFS? SMB/CIFS? What?
When you say “no connection” it means nothing, you have to specify what
protocol you are using.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
So, you have got to download my bash script S.A.C.T. and give it a try. There is no way with the info you have provided so far to give back to you exact details as to what to edit or not. For instance, the openSUSE firewall when turned on, which we recommend, does not by default allow a samba share to work. My bash script can do it all for you, but I can’t jump over the net and push the buttons for you to make it work. Some self help on your part is required. Read through my blog if you are serious and want this to work.
I went into Yast, opened the Samba server and went thru to set access and got the thing to now allow me to open the shares from a Windows machine so I can see them, write to them and that’s what I wanted. I’m not sure it’s perfect but it seems I can deal with the files at this point. A lot better thn getting Suse’s refusal to even open the shares directory up to now.
That’s all I wanted was to be able get to the shares and files and work on them in the Suse box. It’s not that I need critical access - I just want get to the files and process them as tho’ they were on the local box. Maybe this will work for now…
Thanks for the response - I’m just trying to get educated on this Suse OS - it’s a bit different than the others - including the grief to make a working backup and boot it without a problem. Another learnig experience, I presume…
On 2013-08-10 19:36, texasjim wrote:
> That’s all I wanted was to be able get to the shares and files and work
> on them in the Suse box. It’s not that I need critical access - I just
> want get to the files and process them as tho’ they were on the local
> box. Maybe this will work for now…
If that includes the files having the same permissions, owners, etc, you
can not use samba: you need nfs. Samba is Windows style, nfs is Linux style.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)