Tell me more about the loading of bindings, Maybe I will change the load
order and get results?
Darryl
Matthew Hoover wrote:
>
> Enable IP Forwarding in the TCP/IP Properties. (That is if it is not
> already done). Just for everyones knowledge - we had a heck of a time
> getting two NIC's to work in an NTserver. Come to find out, the Nic
> talking to the outside world was required to load up first in the bindings
> section. Who would have known......
>
> Anyway IP forwarding is found under the routing tab. That will allow NT to
> forward IP to the outside world (theoretically). Hope this helps.
> I haven't been keeping up on prior postings to this, so I hope this is not
> a repeat :)
>
> Matt Hoover
> CIOE Corporation
>
> ----------
> > From: Darryl Harvey <darryl@myemail.com.au>
> > To: ntisp@emerald.iea.com
> > Subject: NT Routing ?!?! Help Please !
> > Date: Wednesday, July 16, 1997 4:17 AM
> >
> > Randy Martin wrote:
> > >
> > > At 09:48 AM 7/15/97 -0500, you wrote:
> > > >
> > > >> I am trying to connect a NT Box up to the net on a perm modem
> > > >> connection.
> > > >>
> > > >> The IP's assigned are;
> > > >> 210.8.64.1 was my DUN port.
> > > >> 210.8.64.100 is my Ethernet port (NIC).
> > > >> 210.8.64.0 is my class C (210.8.64/24)
> > > >>
> > > >> The connection works fine, but;
> > > >>
> > > >> 1/. Anything on the internet cannot see the NIC or past it, but can
> ping
> > > >> and see the DUN port.
> > > >> 2/. Anything on the internal LAN can see the NIC card, but not the
> DUN
> > > >> port or outside onto the net. The NT Box is also issuign IP's via
> DHCP
> > > >> on the LAN, so IP is working fine there.
> > > >> > Darryl
> > > >> Darryl@myemail.com.au
> > > >
> > > >Darryl,
> > > >What are you using as software on the NT machine to manage the routing
> or
> > > >proxying that is being done? If you are trying to connect a network to
> > > >another network via the DUN connection something must play the role of
> the
> > > >sever inbetween and bridge those two segments.
> > > >
> > > >You can use Wingate, or Spaghetti, or WinProxy, etc. What are you
> using?
> > > >Just Steelhead or some other routing software?
> > > >
> > > >David Payer
> > > >www.ia-omni.com
> > > >
> > > >
> > > >
> > > > ----------------------------------------------------------
> > > > NTISP Mailing List listserver@emerald.iea.com
> > > >
> > > >
> > >
> > > All you need to do is set the gateway on all the machines (except the
> one
> > > connected to the Internet) to point to the LAN IP address of the
> machine
> > > connected to the Internet. Then set the gateway of that machine's NIC
> to
> > > point to the IP address of the DUN connection. NT server will just
> route.
> > > You don't have to do anything else.
> > >
> > > Using your IPs from above:
> > >
> > > gateway on all machines (except DUN machine) 210.8.64.100
> > > gateway of DUN machine's NIC - 210.8.64.1
> > >
> > > Regards,
> > >
> > > Randy
> >
> >
> > Thanks for your help, but it still doesn't work..
> >
> > 1/. If I assign the gateway address for all "other" machines to the NIC
> > of the "server", then those machines can ping and access the server, but
> > not the outside world.
> > 2/. If I assign the gateway of the Server to the DUN IP, then the server
> > can no longer see the outside world. If I leave the gateway blank, then
> > the Server can see the outside world, but all other machines cannot.
> >
> > The routing table looks like:-
> >
> > Active Routes:
> >
> >
> >
> > Network Address Netmask Gateway Address Interface
> > Metric
> >
> > 0.0.0.0 0.0.0.0 203.63.183.221
> > 203.63.183.221 1
> >
> > 127.0.0.0 255.0.0.0 127.0.0.1
> > 127.0.0.1 1
> >
> > 203.63.183.0 255.255.255.0 203.63.183.221
> > 203.63.183.221 1
> >
> > 203.63.183.221 255.255.255.255 127.0.0.1
> > 127.0.0.1 1
> >
> > 203.63.183.255 255.255.255.255 203.63.183.221
> > 203.63.183.221 1
> >
> > 210.8.52.0 255.255.255.0 210.8.52.100
> > 210.8.52.100 2
> >
> > 210.8.52.100 255.255.255.255 127.0.0.1
> > 127.0.0.1 1
> >
> > 210.8.52.255 255.255.255.255 210.8.52.100
> > 210.8.52.100 1
> >
> > 224.0.0.0 224.0.0.0 203.63.183.221
> > 203.63.183.221 1
> >
> > 224.0.0.0 224.0.0.0 210.8.52.100
> > 210.8.52.100 1
> >
> > 255.255.255.255 255.255.255.255 210.8.52.100
> > 210.8.52.100 1
> > (Which is exactly the same as a working NT server under the same
> > conditions.)
> >
> > 203.63.183.221 = DUN port
> > 210.8.52.100 = NIC
> > a) Server can see internet and LAN, all ok.
> > b) internet can only see DUN IP, cannot see NIC IP or any machine on LAN
> > c) Any machine on LAN can see NIC IP, DUN IP, but not any further on the
> > internet.
> >
> > Note, I now have two different machines (Customers) with this exact same
> > problem, so whatever it is, I need a fix fast.
> >
> > I am lost, any help suggestions appreciated.
> > Darryl
> >
> > ----------------------------------------------------------
> > NTISP Mailing List listserver@emerald.iea.com
> >
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com