Re: Windows Network

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





2008/1/22 max bianco <maximilianbianco@xxxxxxxxx>:


2008/1/22 Dr P Dupre <pd520@xxxxxxxxxx>:


> Dr P Dupre wrote:
>> Hello,
>>
>> I am still trying to configure properly to have this "network" working.
>> Now I can see the other machines on the network !
>> When I try to connect on one (for example belonging to the same workgroup),
>> I get: Sorry, couldn't display all the contents of "Windows Network:
>> bernath" and any machine shows up.
>> Concerning samba, I have: workgroup bernath
>> Security Authentication Mode User
>> Authentification Server: *
>> No Guest Account
>> Encrypt Password yes
>>
>> Concerning the firewall, I enable mail, ssh, samba
>> I did not notice any difference if the SELinux Setting is enforced or
>> disabled.
>>
>> What else should I check ?
>>
>> In the workgroup bernath there is several machines which are visible
>> from a XP machine.
>>
>
> Try connecting to one of the machines by IP address. Do this:
>
> Places>Connect to Server>   When the dialog box pops up change the service
> type to Windows Share and on the line below that where it says server , enter
> the IP address of the XP box. Then hit connect. When prompted for login
> credentials, you must use a user name and password that have an account on
> the local machine you are connecting to.
>
This works, as well as
smbclient -L //  -I
That way I need the ip address.

So you can connect that way?


By the way, something seems wrong with my linux machine.
If I do ping homere (or homere.  and the name of the network) it does
not work from the Linux, but works very well from a XP machine !!!
homere is a XP machine.

Have you looked up Samba using google?Have you read any of the information?
try pinging the machine by  IP  not name. Does this work?

Open the NFS4 port on the firewall. You may need to restart the firewall service if you do this. Always when playing with the firewall, if opening a port does not work, then first restart the service, if that does not do it then go back and close the open port. Do not leave unnecessary ports open at any time. Google is your friend!!

-Max


Dupre - try informing yourself as max pointed out.
This samba stuff is not a 5min deal if you don't have enough information.

On the linux machine the firewall could be a probable problem, you may need
to play with the iptables command and check/open access to your samba
client. I'm not sure how much security is important to you.

As other have said, exercise your Google-ing skills.

~af

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux