I have two RH9 machines and two W2k machines all connected through a switch.
One of the W2k machines uses Internet Connection Sharing and this provides
minimal DHCP ( I think ). Doing but installing RH9 and telling it to use
DHCP will let both of the RH machines surf the net through the W2k machines
dial up connection.

Most of the time clicking on the "Network Servers" app on a RH machines menu
will let me see the Windows workgroup and double clicking the workgroup will
let me access, after giving the username and password, the shared drives on
the windows machines.

Opening "My Network Places" on the windows machines does not show the RH
machines.

I am able to move files back and forth from a RH machine to a Windows
machine but can't move them from RH to RH nor can I use a windows machine to
access either RH machine.

I have not started samba or even done anything to it at all but I can access
the windows machines from the redhat machines.

What must I do to make the windows machines "see" the redhat machines?

cmsix

[ Post a follow-up to this message ]

I guess that setting up SAMBA on the RH machines would solve your
problem. For sharing files among the RH machines you could use NFS. I
don't know RH9, but how do you copy files from Windows to RH ?

cheers
Frank

cmsix wrote:
quote:

> I have two RH9 machines and two W2k machines all connected through a switc
h.
> One of the W2k machines uses Internet Connection Sharing and this provides
> minimal DHCP ( I think ). Doing but installing RH9 and telling it to use
> DHCP will let both of the RH machines surf the net through the W2k machine
s
> dial up connection.
>
> Most of the time clicking on the "Network Servers" app on a RH machines me
nu
> will let me see the Windows workgroup and double clicking the workgroup wi
ll
> let me access, after giving the username and password, the shared drives o
n
> the windows machines.
>
> Opening "My Network Places" on the windows machines does not show the RH
> machines.
>
> I am able to move files back and forth from a RH machine to a Windows
> machine but can't move them from RH to RH nor can I use a windows machine 
to
> access either RH machine.
>
> I have not started samba or even done anything to it at all but I can acce
ss
> the windows machines from the redhat machines.
>
> What must I do to make the windows machines "see" the redhat machines?
>
> cmsix
>
>

[ Post a follow-up to this message ]

"Frank Døssing" <fank@emigrantos.dk> wrote in message
news:3f8b1236$0$45344$edfadb0f@dread11.news.tele.dk...
quote:

> I guess that setting up SAMBA on the RH machines would solve your
> problem. For sharing files among the RH machines you could use NFS. I
> don't know RH9, but how do you copy files from Windows to RH ?


That is something that had me very confused. After the install, I opted for
everything, I was looking around on the start menu and found "Network
Servers." I clicked it, it opened a window and in a few seconds it put up an
Icon for "BOZONET" which is the name of my Windows workgroup. I clicked the
icon and it showed me the three windows machines in the workgroup. I clicked
on one of the machines and it asked for a password, I provided it and then
it showed me the shared drive and I was able to use it like any other shared
drive on a windows network.

I could copy files, move files or edit files. The linux machine does not
show up in any of the Windows machines "Network Neighborhood" though.

After looking around some I think that samba got some type of rudimentary
setup during the installations. The "Network Servers" icon from the start
menu of the Red Hat Machine opens Nautilus, which is some type of file
browser.

I've looked for documentation on Nautilus but can't find any that is useful
for the version I have, 2.2.1 There is a new version out 2.4.x but the
documentation doesn't seem to match what I see when I use the program.

I now believe that I need to work on getting samba set up correctly. I was
confused at first about this because I didn't realize that samba was set up
at all.

I not think that I need to be reading and stufying things myself instead of
asking questions in a newsgroup. I'd rather discover how to make it work
myself than have someone tell me how to do it. I don't really have a
specific use for any linux machines and just started a couple because I had
the hardware and wanted to see what it was like.

Thanks though for replying to my post.

cmsix
quote:

>
> cheers
> Frank
>
> cmsix wrote: 
switch.[QUOTE] 
provides[QUOTE] 
machines[QUOTE] 
menu[QUOTE] 
will[QUOTE] 
on[QUOTE] 
machine to[QUOTE] 
access[QUOTE] 
>

[ Post a follow-up to this message ]

cmsix wrote:
quote:

> I have two RH9 machines and two W2k machines all connected through a
> switch. One of the W2k machines uses Internet Connection Sharing and
> this provides minimal DHCP ( I think ). Doing but installing RH9 and
> telling it to use DHCP will let both of the RH machines surf the net
> through the W2k machines dial up connection.
>
> Most of the time clicking on the "Network Servers" app on a RH
> machines menu will let me see the Windows workgroup and double
> clicking the workgroup will let me access, after giving the username
> and password, the shared drives on the windows machines.
>
> Opening "My Network Places" on the windows machines does not show the
> RH machines.
>
> I am able to move files back and forth from a RH machine to a Windows
> machine but can't move them from RH to RH nor can I use a windows
> machine to access either RH machine.
>
> I have not started samba or even done anything to it at all but I can
> access the windows machines from the redhat machines.
>
> What must I do to make the windows machines "see" the redhat machines?
>
> cmsix


Can you point me to any resources about how I go about networking RH and
Windows 2000 and Internet Connection Sharing?
I have to connect through ISDN and unfortunately I have a USB TA rather than
a serial, which connects through a USB2 Cardbus on my Laptop. RH9 doesn't
recognise either :-( and so I had a brainwave! Network with the W2K machine
and use that as the Internet Connection. But I need some pointers.

Thank you.

[ Post a follow-up to this message ]

Rifleman wrote:
quote:

> cmsix wrote: 
>
> Can you point me to any resources about how I go about networking RH and
> Windows 2000 and Internet Connection Sharing?
> I have to connect through ISDN and unfortunately I have a USB TA rather
> than a serial, which connects through a USB2 Cardbus on my Laptop. RH9
> doesn't recognise either :-( and so I had a brainwave! Network with the
> W2K machine and use that as the Internet Connection. But I need some
> pointers.
>
> Thank you.


Well, Rifleman, I can't help with much, but I can help with W2K Internet
connection sharing. It doesn't require anything more than a TCP/IP link. To
share the connection on the windoze box, just right-click my network
places, select properties, right click the internet connection you want to
share, select properties again, then the sharing tab. Check the "share this
connection" box. It will change the IP address of your LAN interface to
192.168.0.1 (so you need one interface connected to your LAN and another to
the internet [WAN]). You can change it to whatever you want once ICS is set
up. The only thing is that you can't have a default gateway on the LAN
interface, just the WAN side. If you stay with the ICS default
192.168.0.x/24 network, ICS will also dish out DHCP addresses complete with
DNS servers, and gateway. This is handy if you are getting your WAN info
via DHCP from your ISP.

On the RH boxes, just make sure they are on the same network as the Windows
LAN adapter, and that you can ping the LAN adapter on the windows box. For
manual setup, set the gateway on the RH machines to point to the windows
LAN address, and point DNS to your ISPs DNS server. ICS will NAT and route.
I've got this exact setup running right now and I'm typing this message
using it.

ICS also lets you forward ports for incoming traffic to inside machines, so
I can terminal-serve to my windows machine, ssh or vnc to my Linux box,
etc.

BTW, you can do this with one card if it has an IP address on both networks,
but it's real flakey. Separate physical NICs, one on each network, is the
way to go.

[ Post a follow-up to this message ]

Thanks for the info!

"Kurt L" <kurtl@olypen.com> wrote in message
news:vprr1so80ijed1@corp.supernews.com...
quote:

> Rifleman wrote:
> 
>
> Well, Rifleman, I can't help with much, but I can help with W2K Internet
> connection sharing. It doesn't require anything more than a TCP/IP link.

To
quote:

> share the connection on the windoze box, just right-click my network
> places, select properties, right click the internet connection you want to
> share, select properties again, then the sharing tab. Check the "share

this
quote:

> connection" box. It will change the IP address of your LAN interface to
> 192.168.0.1 (so you need one interface connected to your LAN and another

to
quote:

> the internet [WAN]). You can change it to whatever you want once ICS is

set
quote:

> up. The only thing is that you can't have a default gateway on the LAN
> interface, just the WAN side. If you stay with the ICS default
> 192.168.0.x/24 network, ICS will also dish out DHCP addresses complete

with
quote:

> DNS servers, and gateway. This is handy if you are getting your WAN info
> via DHCP from your ISP.
>
> On the RH boxes, just make sure they are on the same network as the

Windows
quote:

> LAN adapter, and that you can ping the LAN adapter on the windows box. For
> manual setup, set the gateway on the RH machines to point to the windows
> LAN address, and point DNS to your ISPs DNS server. ICS will NAT and

route.
quote:

> I've got this exact setup running right now and I'm typing this message
> using it.
>
> ICS also lets you forward ports for incoming traffic to inside machines,

so
quote:

> I can terminal-serve to my windows machine, ssh or vnc to my Linux box,
> etc.
>
> BTW, you can do this with one card if it has an IP address on both

networks,
quote:

> but it's real flakey. Separate physical NICs, one on each network, is the
> way to go.

[ Post a follow-up to this message ]