Prev: mtink?
Next: Wireless card doesn't work after kernel update on openSUSE 10.3
From: PaulRS on 31 Jan 2008 21:28
SuSE 10.3 Retail - New Installation

Small 3 cumputer home network - 1 Suse 10.3 ; 2- Win2000

I set up Samba under YAST as directed in the documentation (Retail
Book)

(1) In the Browser, Samba sees the network and all three computers
(2) Clicking on the SuSE computer brings up the shares
(3) Both windows computers see all three and also see the SuSE
computer shares

(4) PROBLEM: In SuSE, clicking on either of the two windows
computers give an error - Unable to connect.
Entering a more direct command into the browser to one of the
directories shared by a windows computer yields the message that "win
(computername) times out" error.

What am I missing??
Any help

Paul

--

From: PaulRS on 1 Feb 2008 20:13
On Thu, 31 Jan 2008 02:28:41 UTC, "PaulRS" <prschmi(a)Zverizon.net>
wrote:

> SuSE 10.3 Retail - New Installation
>
> Small 3 cumputer home network - 1 Suse 10.3 ; 2- Win2000
>
> I set up Samba under YAST as directed in the documentation (Retail
> Book)
>
> (1) In the Browser, Samba sees the network and all three computers
> (2) Clicking on the SuSE computer brings up the shares
> (3) Both windows computers see all three and also see the SuSE
> computer shares
>
> (4) PROBLEM: In SuSE, clicking on either of the two windows
> computers give an error - Unable to connect.
> Entering a more direct command into the browser to one of the
> directories shared by a windows computer yields the message that "win
> (computername) times out" error.
>
> What am I missing??
> Any help
>
> Paul
>

OK - By experimentation I discovered the basis of my problem. Samba
cannot fiqure out the IP address of a named computer. When I looked
up the current network address 192.168.1.100 of the "windows2000" box
and entered it into /etc/HOSTS, Samba worked.

Problem is that my mini network works by DHCP and the final number
will vary between 100-103 depending which computer boots up first.
- any suggestions??



--

From: Stuart Miller on 2 Feb 2008 01:54

"PaulRS" <prschmi(a)Zverizon.net> wrote in message
news:bEnW4COosC69-pn2-4qZmPO8IKEFj(a)localhost...
> On Thu, 31 Jan 2008 02:28:41 UTC, "PaulRS" <prschmi(a)Zverizon.net>
> wrote:
>
>> SuSE 10.3 Retail - New Installation
>>
>> Small 3 cumputer home network - 1 Suse 10.3 ; 2- Win2000
>>
>> I set up Samba under YAST as directed in the documentation (Retail
>> Book)
>>
>> (1) In the Browser, Samba sees the network and all three computers
>> (2) Clicking on the SuSE computer brings up the shares
>> (3) Both windows computers see all three and also see the SuSE
>> computer shares
>>
>> (4) PROBLEM: In SuSE, clicking on either of the two windows
>> computers give an error - Unable to connect.
>> Entering a more direct command into the browser to one of the
>> directories shared by a windows computer yields the message that "win
>> (computername) times out" error.
>>
>> What am I missing??
>> Any help
>>
>> Paul
>>
>
> OK - By experimentation I discovered the basis of my problem. Samba
> cannot fiqure out the IP address of a named computer. When I looked
> up the current network address 192.168.1.100 of the "windows2000" box
> and entered it into /etc/HOSTS, Samba worked.
>
> Problem is that my mini network works by DHCP and the final number
> will vary between 100-103 depending which computer boots up first.
> - any suggestions??
>

1) avoid dhcp, set each machine to have manually assigned ip address

2) in the event that #1 is not possible, set up router to always assign a
specific ip address to a specific MAC address. Same effect as #1

#2 is preferred if your laptop will be visiting hotspots.

There are a few more options, try these first

Stuart


 | 
Pages: 1
Prev: mtink?
Next: Wireless card doesn't work after kernel update on openSUSE 10.3