Nominee: "Duh!" of the month club award! Paul, you hit the nail right on the head! What makes it a double "Duh!" for me is that I've been looking at that paramater for weeks, & never made the connection. . . Solution: In an NT based network, the DHCP settings apparently -OVERRIDE- the locally set settings, (instead of the reverse being true), so when I set the default gateway -locally- to point to the STN box, but had the "router" paramater blank in the DHCP paramaters, the "blank" setting won. Ergo, no default router/gateway. When I set up STN's DHCP, it populated that setting - and things began to work! I have now turned off the STN DHCP, and restored the NT scope, (with paramater 3 set!), and it still works. Thanks yet again. Jim Paul R. Johnson wrote: > This may be an oops because I just realized that you were dailing and > that may be related. I'll give you the setup anyway. > > On our internal net, we are using 10.100.100.x > STN is at 10.100.100.1 > DHCP has the following Global Options set: > 003 Router 10.100.100.1 > 006 DNS Servers 10.100.100.1 > 044 WINS Servers 10.100.100.10, 10.100.100.20 > 046 WINS/NBT Node Type 0x8 (Hybrid) > > While we are connected to Dsl, it works for us. Don't know about the > dialup. Sorry that I just realized that part. It's been a long week. > > Paul > > --- Jim Harris <[EMAIL PROTECTED]> wrote: > > Paul, > > > > I would not be suprised if that were true. . . > > > > Can you tell me exactly how -YOU- set it, (i.e which paramater, > > where?) > > > > I found that if the STN box was not doing the DHCP, even if the PDC, > > (and client machines) had the STN box hard-coded as the default > > gateway, > > it would not route. Routing only happened when I turned on STN's > > DHCP > > features. > > > > Jim > > > > Paul R. Johnson wrote: > > > Is it possible that your Gateway in your NT DHCP scope was not set > > > properly? I am running an NT network with both STN adapters > > configured > > > staticly (is that a word?) and it all works just fine with NT's > > DHCP. > > > I much prefer the DHCP in NT because it is easy to set the node > > type, > > > WINS addresses, and other options. > > > > > > Paul > > > > > > > > > --- Jim Harris <[EMAIL PROTECTED]> wrote: > > > > I found a solution - and I want someone to explain this to me. . > > . > > > > > > > > 1. I tried everything but burning brown rice and sacrificing > > small > > > > rodents to my computer. Set just about every nameserver and DNS > > > > option > > > > I could think of, including leaving them blank. I even tried > > "home" > > > > as > > > > a domain entry! (which got old fast. . .) > > > > > > > > 2. I then turned on DHCP. (I had noticed that there were issues > > with > > > > > > > > DNS not being enabled either) > > > > > > > > Previous to this, I was using my NT PDC as a DHCP server, with my > > STN > > > > > > > > box statically addressed. This time, I turned off the DHCP scope > > on > > > > my > > > > NT box, (disabling DHCP), blew away all the NT boxe's leases, > > cleared > > > > > > > > the DHCP on my client machine, booted STN, and now it works. (I'm > > > > using > > > > it now). > > > > > > > > I want someone to explain to me why this #%*&! thing would -not- > > > > route > > > > until I turned on DHCP? Why does it not even -dial- unless DNS > > is > > > > enabled? > > > > > > > > Jim (the confused!) > > > > > > > > Jim Harris wrote: > > > > > Patrick, > > > > > > > > > > Been there, done that, bought the tee-shirt! > > > > > > > > > > I tried setting the dns nameserver to a known nameserver on my > > ISP. > > > > > > > > > Actually, that is one of the -first- things I tried. . . . > > > > > > > > > > (I also discovered, that if I do -NOT- set DNS enabled, the > > modem > > > > would > > > > > never dial) > > > > > > > > > > Still no joy. > > > > > > > > > > One of the reasons I think it is a -routing- issue, is that if > > I do > > > > > > > > > -not- use nameservices at all in my call, and try to connect > > > > directly to > > > > > > > > > > an IP address (no name service necessary!) it still does not > > route. > > > > > > > > > > Just when I'm thinkin' I'm on the top of the world, something > > like > > > > this > > > > > comes along just to humble me! (grin!!) > > > > > > > > > > Thanks for the help. > > > > > > > > > > Jim > > > > > > > > > > > > > > > Patrick Belliotti wrote: > > > > > > At 09:30 AM 3/27/00 -0800, you wrote: > > > > > > >I'm futzin' around with this, and ran into a bit of a > > problem. > > > > > > > > > > > > > >I have a network within the ip space of 172.31.*.*, > > 255.255.0.0 > > > > > > > > > > > > > >I can build a disk, and see STN at its address (say > > > > 172.31.100.1) > > > > > > > > > > > > > >I have (on the internal network tab), the name server set to > > the > > > > same > > > > > > >address. > > > > > > > > > > > > That's wrong. This should either be blank or the IP your ISP > > > > gave you. > > > > > > > > > > > > This is from STN's own help file: > > > > > > > > > > > > Name Svr > > > > > > Knowing what IP address to put here can be tricky. Here's > > the > > > > rundown: > > > > > > > > > > > > � If you are using ShareTheNet's integrated DNS Server > > (chosen on > > > > the > > > > > > Options Tab), you can either leave this blank or enter the IP > > > > address of > > > > > > > > > > > > the DNS server that your ISP gave you. If you leave it > > blank, > > > > then > > > > > > ShareTheNet will use the top level DNS servers directly, > > > > bypassing your > > > > > > ISP's name servers completely. This will normally be slower > > than > > > > using > > > > > > your ISP's name server. > > > > > > � If you are using ShareTheNet's integrated DNS Server and > > you do > > > > not > > > > > > leave it blank, then you will use your ISP's name servers for > > > > queries > > > > > > that are not fulfilled by the integrated DNS server. > > > > > > > > > > > > � If you are not using ShareTheNet's integrated DNS Server, > > and > > > > your ISP > > > > > > > > > > > > uses DHCP to configure your cable modem or ADSL modem, then > > you > > > > should > > > > > > still leave this blank. > > > > > > � If you are not using ShareTheNet's integrated DNS Server, > > and > > > > your ISP > > > > > > > > > > > > does not use DHCP to configure your connection, then you > > should > > > > put the > > > > > > IP address that your ISP gave you for name service here. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >I have configured the net features, DNS, no DHCP, all the > > > > monitoring > > > > > > >tools except TCPDUMP. > > > > > > > > > > > > > >I can connect to my ISP directly via modem, and via an NT > > Proxy > > > > Server > > > > > > >II also using a modem. > > > > > > > > > > > > > >I cannot get STN to route to the outside net. > > > > > > > > > > > > > >I even tried setting the name server address within STN to > > the > > > > address > > > > > > >of a known nameserver on the external net. > > > > > > > > > > > > > >If I try to reach a named resource (i.e. www.dogpile.com) it > > > > cannot > > > > > > >resolve the name. If I try to reach a resource by IP, it > > says > > > > the > > > > > > >network is not reachable. > > > > > > > > > > > > > >What am I doing wrong? How do I get 172.31.*.* to route to > > the > > > > rest of > > > > > > >the void? > > > > > > > > > > > > Not a routing problem at all. When DNS is hosed, lots of > > stuff > > > > fails... > > > > > > > > > > > > > > > > > > > >Jim > > > > > > >-- > > > > > > >Visit http://www.ShareTheNet.com for info about ShareTheNet > > > > > > >Visit http://www.topica.com/lists/sharethenet for info about > > > > this list > > > > > > >_________________________________________________________ > > > > > > >Enlighten your in-box. http://www.topica.com/t/15 > > > > > > > > > > > > > > > > > -- > > > > Visit http://www.ShareTheNet.com for info about ShareTheNet > > > > Visit http://www.topica.com/lists/sharethenet for info about this > > > > list > > > > _________________________________________________________ > > > > Enlighten your in-box. http://www.topica.com/t/15 > > > > > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Talk to your friends online with Yahoo! Messenger. > > > http://im.yahoo.com > > -- > > Visit http://www.ShareTheNet.com for info about ShareTheNet > > Visit http://www.topica.com/lists/sharethenet for info about this > > list > > _________________________________________________________ > > Enlighten your in-box. http://www.topica.com/t/15 > > > > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.com -- Visit http://www.ShareTheNet.com for info about ShareTheNet Visit http://www.topica.com/lists/sharethenet for info about this list _________________________________________________________ Enlighten your in-box. http://www.topica.com/t/15
