Topic: Primary/Secondary DNS

[Jeff Fentum]

I'm running out of hope/options here...please HELP!

I'm lacking some experience with both routers and e-smith servers, so please bear with me.

I need to know if there is a way to add primary and secondary DNS lookup assignment numbers to v5.1.2 SME Server's configuration. I'm not really sure if I need to, but it might help.

Here's the problem:

I've loaded v5.1.2 SME Server on a freshly-built platform. All of the components were checked for compatability, especially the NICs, which is a 3Com XXXXX. I performed the installation without a hitch. Can I see the server on the local network? Yes, it shows. Now, can I ping the server's external address. Nope. No response. I then test to see if the card is compatable by swapping port assignments. Both cards work for local. Neither works for outside. I continue to troubleshoot. I call my ISP to go over the settings for my Cayman DSL router. I confirm the correct entries for my external configuration. Nothing works. The Internet test on the consol fails and I can't ping the box.

Now here's the punchline. I wiped the installation of v5.1.2 out and loaded Redhat 7.0 with the same network parameters as before, but with the Primary and Secondary DNS numbers assigned, and it works like a champ (Apache test page comes up first try). So what's the problem? Is it v5.1.2? Should I try v5? Do the DNS numbers matter (the techie at my o-so-friendly ISP says NO)? If not, why does it fail when they're not used?

Tech Notes: The DNS numbers begin with a 151.164.XX.XX, my static IP address starts with 65.71.XXX.XXX. The 151.164.XX.XXX lookup numbers were setup in the Cayman router, but the ISP's tech rep said that the router doesn't use the lookup numbers. So why assign them in the router's setup if they're not used!? I also asked if the router was supposed to direct the destinaton of the outgoing packets, and he said NO. Isn't that what router is supposed to do?

Sorry if this is a little long-winded, but frustration is beginning to cripple my communication skills...

[Charlie]

You don't need DNS to ping. Since you can't ping the external nic, the problem is somewhere in the E-smith box. I would suggest removing the external nic and putting in a cheap Realtek 8139 chip based nic. I can get them for $10.  Linux works very well with this chipset.

[Jeff Fentum]

What really puzzles me is that Redhat 7.0 can use the 3com card without any problems. But both v5 and v5.1.2 of SME server can't, at least when it's used as the external port. Works fine when used as local. What gives?

I did order an Intel NIC (pro100) since I tried to make do with a useless Dlink NIC that I got from my ISP when the ADSL service was connected. If the Intel card dead ends me I may give up on SME server. Don't want to, but I have to go with what I can get to work...

Thanks...

[Lynn]

The SME Server doesnt seem to respond to pings. This is actually a good thing, but not helpful when trouble shooting. It doesnt allow pings through it either - you cant ping the outside world from a client PC.

So, you have to ping from the SME Server itself.

Have SME go to a command prompt at boot rather than to the console automatically. This is a choice during the configuration.

Then, enter root, and enter the admin password. This takes you to a command prompt.

Type in:  ping 192.43.244.18.

Thats the NTP Time server I use. Some servers reply to pings and some don't, so you have to use one you know will respond. You could also try pinging www.somedomain.com.

Enter exit to leave. And enter admin, plus the password to get to the console.

Anyway, you probably are up, but dont have all the settings finished.