Hey Rusty...did you read what you wrote.
You start out by suggesting that my answer about routing and pinging wasn't
the issue and then end up asking the same question that I did.
Mike revisits original question...
> I really feel stupid now: I never thought about
> any settings on the NT box.
> Yes, I can ping the nt box from the 192.168.3.0
> network. The gateway on the nt box sounds like it
> could be the problem. I was thinking about setting the
> nt box with these settings:
> IP:192.168.2.2
> MASK:255.255.0.0
> GATE:192.168.3.1
>
> Does this sound reasonable?
> I am not worried about the nt box having access to the
> internet: there is no need for that.
---
Actually routing is probably the issue and assuming that your NT computer
can ping the various other computers that it is going to "WINDOWS" network
with, then
on the same subnet you don't need a WINS server
on any other subnet, you need the help of a WINS server - you can set up a
WINS server to broadcast to a remote subnet - Even Samba can act as a WINS
server and do remote broadcasts.
Your scheme for subnet mask listed above is less than an optimal choice.
your subnet mask with the above IP and Gateway addresses need only be
255.255.254.0 - the one you listed was for a class B which is way too broad
for your usage.
You don't need a domain controller at all. It has nothing to do with
anything except controlling access to network resources/shares.
Craig
----:----|----:----|----:----|----:----|----:----|----:----|
- Craig White - PO Box 8634 - Scottsdale, Arizona - 85252
- e-mail address ................ -
CraigWhite@AzApple.com
- world wide web address ........ -
http://www.AzApple.com
- e-mail my pager address ....... -
6023779752@airtouch.net
- cellular phone ................ - (602) 377-9752
- voice/facsimile ............... - (480) 945-8445
----:----|----:----|----:----|----:----|----:----|----:----|
> -----Original Message-----
> From: plug-discuss-admin@lists.plug.phoenix.az.us
> [mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of Rusty
> Carruth
> Sent: Friday, July 10, 2893 4:44 PM
> To: plug-discuss@lists.plug.phoenix.az.us
> Subject: Re: network question
>
>
> >
> > get more basic...can you ping any of the other computers from
> your Windows
> > NT Box? can you ping the linux box from your Windows NT Box.
>
> Well, that is a good question, but I think the problem is not routing
> IP, but routing Samba.
>
> > > [mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of Mike
> > > Starke
> > >
> > > I'm stumped. I have two networks:
> > > 192.168.2.0/24
> > > 192.168.3.0/24
> > >
> > > I have a NT Server on the 192.168.2.0 network. I have a linux
> > > box masquerading IP's for the 192.168.3.0 network. SHouldn't
> > > I be able to have my Win9X PC's log into the NT Server from the
> > > 192.168.3.0 network?
>
> you need to pass Samba traffic through whatever you are using to
> do the IP routing between networks. What is your router? Also,
> I think (now I'm starting to talk from what I *think* is right,
> but I have not gotten far enough along in SMB networking to
> know for sure if what I am saying is even SANE, much less RIGHT!)....
> So, I *think* you will need a domain controller or something like
> that to share domain info across the subnets.
>
> Anybody know the REAL answer to that? HOw does that work?
>
> > > All other TCP/IP works just fine. Telnet , FTP, WWW, etc can all
> > > go from 192.168.3.0/24 to 192.168.2.1 (another linux gateway)
> -> Internet.
>
> this implies:
>
> 1 - don't change your default route! Or you will lose internet.
> 2 - networking is ok, default-wise anyway.
>
> you did not say if you can PING the NT network from the Win9X
> network. If so, then IP routing is ok and its just NT (SMB)
> 'routing' to look at.
>
> > > Any tips?
>
> Try looking at the SMB howto also. (Try to get a recent one)
>
> rusty
>
> _______________________________________________
> Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)