Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
FedoraForum Search

Forgot Password? Join Us!

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 29th February 2008, 05:24 PM
rgaelzer Offline
Registered User
 
Join Date: Oct 2005
Location: Rio Grande do Sul, Brazil
Posts: 135
Windows shares not accessible after standard configuration

I'm trying to access my windows workgroup to use the printer and for file transfer.
I used only the configuration apps that come with fedora 8 to set it up.

First of all, using system-config-firewall, I included Network Printing (IPP) (Port/Protocol: 631/tcp, 631/udp) and Samba (Port/Protocol: 137/udp, 138/udp, 139/udp, 445/tcp) as Trusted Services.

Then, using System-Config-Printer, I tried to include the windows printer. Selecting New Printer -> Windows Printer via SAMBA, it was able to automatically detect the workgroup (UNIVERSE), the host (QUASAR) and the printer (hp940c). After choosing the appropriate driver, the app created the queue with the correct Device URI (smb://UNIVERSE/QUASAR/hp940c), but the Test Page printing was unsuccessful. When I tried to change the Device URI, clicking on the Verify button, it reported that "This print share is not accessible", even when I tried to authenticate with an existing user on QUASAR.

Moreover, when I tried to access the shared folders using konqueror, by clicking on System -> Remote Places -> Samba Shares, it would locate the workgroup (Universe), but would not access it, issuing the error message: "Timeout on Server universe".

I did the following tests:

1) Disabling the firewall on the fedora host does not solve the problem.
2) Disabling the firewall on the windows host also does not solve the problem. I still don't access the workgroup.
3) Using another windows host on my LAN, I can access the workgroup universe all right.

After this point, I got kinda stuck.

Could this be a SELinux issue? I'm somewhat afraid to screw with SELinux. Using system-config-selinux, I notice that I have only the following boolean variable active: samba_run_unconfined

Anyone could give me a hint?
__________________
Rudi Gaelzer
Registered Linux user # 153741
Reply With Quote
  #2  
Old 29th February 2008, 08:33 PM
ppesci's Avatar
ppesci Offline
Registered User
 
Join Date: May 2006
Location: Caracas, Venezuela
Posts: 1,828
Maybe you must to remove the workgruo from the URI, that is:

smb://UNIVERSE/QUASAR/hp940c

must be

smb://QUASAR/hp940c

in cups.

In konqueror, to see the shares in QUASAR server, yust use:

smb://QUASAR

HTH
__________________
Pietro Pesci Feltri

PowerBook 15" G4 and
MacBook Pro 17" Intel Core 2 Duo
Intel I5 Desktop
Reply With Quote
  #3  
Old 29th February 2008, 09:50 PM
rgaelzer Offline
Registered User
 
Join Date: Oct 2005
Location: Rio Grande do Sul, Brazil
Posts: 135
Thanks for the suggestion,but it didn't work. Getting rid of the workgroup is not the answer...
__________________
Rudi Gaelzer
Registered Linux user # 153741
Reply With Quote
  #4  
Old 1st March 2008, 04:23 AM
ppesci's Avatar
ppesci Offline
Registered User
 
Join Date: May 2006
Location: Caracas, Venezuela
Posts: 1,828
Can you try in konqueror the URL:

smb://QUASAR/some_share

Where you must substitute some_share of course

Put the URL manually,do not use Remote Places

On the other side, you are using Linux as client, not as server, the firewall configuration services is used when Linux is server I think. Do not believe the problem is a firewall in Linux anyway.
__________________
Pietro Pesci Feltri

PowerBook 15" G4 and
MacBook Pro 17" Intel Core 2 Duo
Intel I5 Desktop
Reply With Quote
  #5  
Old 2nd March 2008, 11:17 PM
swerdna's Avatar
swerdna Offline
Registered User
 
Join Date: Apr 2007
Posts: 10
Try using smb://ip.address.of.quasar, just to check network connectivity is OK. This takes you down one level of complexity by cutting out name resolution. I'm not suggesting using this permanently instead of smb://netbios_name_of_server. It's a diagnostic suggestion.

Swerdna
Reply With Quote
  #6  
Old 23rd March 2008, 06:23 PM
rgaelzer Offline
Registered User
 
Join Date: Oct 2005
Location: Rio Grande do Sul, Brazil
Posts: 135
Indeed, using directly the ip number works. I can print that way. However, since the win box uses dhcp, that number can eventually change.

I noticed that the winbind deamon is not running. Does it have anything to do with my problem here?
__________________
Rudi Gaelzer
Registered Linux user # 153741
Reply With Quote
Reply

Tags
accessible, configuration, shares, standard, windows

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Samba Shares not accessible Tekno_Cowboy Servers & Networking 8 19th January 2009 11:58 PM
Samba shares not accessible after reboot in FC9 AndrejaKo Servers & Networking 14 6th January 2009 04:13 PM
Standard Kernel Processor Configuration vtomov Installation and Live Media 4 24th February 2005 05:54 PM


Current GMT-time: 02:13 (Wednesday, 22-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat