I remember that I had some issues similar to this, but It was different
in my case. I run a mail server and webserver on a machine inside the
firewall. I port forward port 80 and port 25 to the internal server. I
had to add an entry to my /etc/hosts so that my internal machine
(192.168.10.10) had the same domain name as my firewall machine. This
fixed problems that I was having with qmail. I don't think that you need
to exactly do this, but you may need to add an entry to you /etc/hosts
for you internal machine to able to resolve itself.
JDF
>Alex Hewitt USG wrote:
>
> Yes. I knew they logged the MAC address and called them to change from the
> NIC in my main system to the WAN MAC address of the router. It worked
> immediately. BTW, managing the router is pretty easy. You simply plug the
> router's LAN IP address into your browser and the router has built-in
> routines to let you manage it. You can enable/disable DHCP, expose
> specific LAN IP address to the WAN, etc..
>
> The problem with only having the Mediaone DNS is that there isn't a DNS
> for the LAN (unless you set one up). That might be another possible
> solution.
>
> -Alex
>
> Wirth's Law: Software gets slower faster than Hardware gets faster!
>
> "On the side of the software box, in the 'System Requirements' section, it
> said 'Requires Windows 95 or better'. So I installed Linux." - Anonymous
>
> On Tue, 18 Jul 2000, Cole Tuininga wrote:
>
> > Alex Hewitt USG wrote:
> > >
> > > A few days ago I bought a LinkSys DSL/cable modem firewall router for my
> > > home lan which is connected to Mediaone through a cable modem. I decided
> > > to modify my system's setups to use DHCP. The LinkSys router acts as a
> > > DHCP server and each system as it comes on-line queries the server and
> > > gets both an IP address (in the 192.168.1.* range) and the DNS server
> > > addresses for Mediaone.
> > >
> > > However, when I tried to setup my Linux system, the system hung when it
> > > tried to start sendmail and then hung again when it got to the Apache
> > > httpd daemon. I waited for the services to timeout and once I was able to
> > > login, I tried to start X which hung trying to get the host's IP address.
> > > I was temporarily able to correct all of this by editing my /etc/hosts
> > > file and adding the system's hostname and the IP address that the DHCP
> > > server had given it (specifically 192.168.1.101). Somehow this doesn't
> > > quite seem correct. I would expect X to get the IP address of the local
> > > host by some other means than either DNS or the hosts file. Perhaps all of
> > > these services should be using the localhost address?
> >
> > It sounds to me as though you are perhaps having name resolving
> > problems?
> >
> > Keep in mind that with Mediaone the cable modem "knows" the MAC address
> > of the hardware you connect to it so if you even change over to a new
> > NIC, you have to contact Mediaone and have them reset your modem.
> >
> > --
> > I've found Jesus. He was behind the sofa the whole time.
> >
> > Cole Tuininga
> > Network Admin
> > Code Energy, Inc
> > [EMAIL PROTECTED]
> > (603) 766-2208
> >
> >
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
>Alex Hewitt USG wrote:
>
> Yes. I knew they logged the MAC address and called them to change from the
> NIC in my main system to the WAN MAC address of the router. It worked
> immediately. BTW, managing the router is pretty easy. You simply plug the
> router's LAN IP address into your browser and the router has built-in
> routines to let you manage it. You can enable/disable DHCP, expose
> specific LAN IP address to the WAN, etc..
>
> The problem with only having the Mediaone DNS is that there isn't a DNS
> for the LAN (unless you set one up). That might be another possible
> solution.
>
> -Alex
>
> Wirth's Law: Software gets slower faster than Hardware gets faster!
>
> "On the side of the software box, in the 'System Requirements' section, it
> said 'Requires Windows 95 or better'. So I installed Linux." - Anonymous
>
> On Tue, 18 Jul 2000, Cole Tuininga wrote:
>
> > Alex Hewitt USG wrote:
> > >
> > > A few days ago I bought a LinkSys DSL/cable modem firewall router for my
> > > home lan which is connected to Mediaone through a cable modem. I decided
> > > to modify my system's setups to use DHCP. The LinkSys router acts as a
> > > DHCP server and each system as it comes on-line queries the server and
> > > gets both an IP address (in the 192.168.1.* range) and the DNS server
> > > addresses for Mediaone.
> > >
> > > However, when I tried to setup my Linux system, the system hung when it
> > > tried to start sendmail and then hung again when it got to the Apache
> > > httpd daemon. I waited for the services to timeout and once I was able to
> > > login, I tried to start X which hung trying to get the host's IP address.
> > > I was temporarily able to correct all of this by editing my /etc/hosts
> > > file and adding the system's hostname and the IP address that the DHCP
> > > server had given it (specifically 192.168.1.101). Somehow this doesn't
> > > quite seem correct. I would expect X to get the IP address of the local
> > > host by some other means than either DNS or the hosts file. Perhaps all of
> > > these services should be using the localhost address?
> >
> > It sounds to me as though you are perhaps having name resolving
> > problems?
> >
> > Keep in mind that with Mediaone the cable modem "knows" the MAC address
> > of the hardware you connect to it so if you even change over to a new
> > NIC, you have to contact Mediaone and have them reset your modem.
> >
> > --
> > I've found Jesus. He was behind the sofa the whole time.
> >
> > Cole Tuininga
> > Network Admin
> > Code Energy, Inc
> > [EMAIL PROTECTED]
> > (603) 766-2208
> >
> >
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
