Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Using SAMBA to access a PC-BSD System from a Suse Linux v10 System

xdxexf (TechnicalUser) (OP)
6 Nov 06 15:43
11/06/06

Subject;    Using SAMBA to access a PC-BSD System from a Suse Linux v10 System

This longer than I like but I have no other way to describe the problemm accurately.

I have only been using Linux for just over a year now; and the PC-Bsd testing is totally new.

I have spent over 4 longggggggg days trying to find a solution to this problem and did not find anything.
The time spent was doing numerous Google searches and trying any and all the steps suggested at a site where it looked like what was to be done would work.

My systems (I do not believe the physical hardware attributes of the two PCs matter).
1)  Old pc. Primarily using Suse Linux  v10.0 "dual boots" to W2K, WXP,

Testing the following    Fedora v5, PC-Linux OS, and PC-BSD v1.2  
(as I see so many different distros of Linux that I just might switch from Suse should I find
    something better. (And I have not yet))

    Hostname/Compute-Name           oldpca3

2)  New pc.  Primarily using Suse Linux v10.0 "dual boots" to W2K and WXP.
This machine I want as stable as possible as I need to do various projects on it.

    Hostname/Computer-Name           newpca3

Using a Linksys router.

I am using most current version of Samba to network the two PCs together so that:
     a)  I can access the other systems files
     b)  Share the broadband internet connection.
     c)  Possible buy a laptop and using a wireless connection share all things between 3 PCs

Each OS on each PC have, the same names, ID's and anything else possible the same.

Since I access the internet through both machines I use an antivirus software, and a firewall.

The firewall on W2K and WXP (on both machines) is Zone Alarm (most current version)

The firewall in SUSE is running the installed firewall at installation of SUSE onto the PC.

Each testing OS is using the firewall that came with the OS and install by the OS.

I keep both machines up-to-date with fixes, patches and updates  on  a weekly basis.

However,  a system is booted and whatever OS is running it can see the other system's files/partitions  example
1)  Oldpc running SUSE can see and access files on Newpc when it is running SUSE, W2K or WXP
2)  Newpc running WXP can see and access files on Oldpc when it is running SUSE, W2K or WXP
(WXP or W2K cannot see the Linux files when it is running) The point is that each PC can always see the other PC files,

(To be clear)
whichever OS I boot into. I do not need to reboot the other system just because I rebooted one PC. Whatever I boot into on one PC, after it is fully up. I can see each others files.

3)  Now I want to try another OS on the Oldpc to see how it looks and feels. And if I like it (maybe switch to it).

Under/using PC-BSD, on the Oldpc, I set it up and have it running OK .

Setup Samba on PC-BSD to access the Newpc's files, which it does. I can see the Suse files and all the Windows VFat and NTFS partition files.

The problem is I cannot access anything on the PC-BSD system (Oldpc).(I thought it might be the firewalls so I turned them off on both PCs)  

(Using a 5gb Vfat partition for passing files to/from both systems)

When I do a mount of the partition on the Newpc I get the following error:

using the "mount" syntax I get
Error connecting to 192.168.1.101 (No route to host)
6837: Connection to oldpca3 failed
SMB connection failed

using the "smbmount" syntax I get
Error connecting to 192.168.1.101 (No route to host)
19979: Connection to oldpca3 failed
SMB connection failed

Why the difference in the numbers I do not know but I present it as it many help you.

Even if I reboot the Newpc when ir is up and running I can acces it's file from the Oldpc without having to reset Samba or the whole netwoks settings on it.

Numerous reboots, resetting the network, whatever,  I cannot get the Newpc to see/access any files/partitions
on the Oldpc. But the Oldpc (using PC-BSD) can see/access files/partitions on the Newpc.

Due to the fact that I put forth a lot of effort to name everything the same on/under each OS on a PC
that I have no problems with any of the script files or /etc/fstab that do the mounting of the partitions.
(manually typing a partition mount through a console input I get the same errors)

Not knowing where to post (as I can see how this could be a Linux or a PC-BSD problem) I started here at the
Tek-Tips (Samba) forum.  Then I will go to wherever from what I receive here.

Thank you in advance for you answers/directions.
cyoung (Programmer)
9 Nov 06 14:45
Have you verified that 192.168.1.101 is the IP address of oldpca3?

Can you ping that IP address and get a response?

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close