[EMAIL PROTECTED] wrote:
>
> We already utilize DNS in the way you describe. The folks that
> maintain our corporate network are always pressing us give up
> our static addressing for our AWs. That's really my only
> driver for asking about DHCP. My comments about DNS were
> probably misleading.
>
> Thanks,
> Jim
You could set up your AW's second ethernet ports onto a free address
range such as 192.168.x.x. These addresses are not legal addresses on
the Internet. That way you can make them static if you wish, and I would
recommend that.
To access these addresses from other subnets within your organisation
you will require a router to route between this subnet and the others.
You could alias one of the AW's ethernet ports to do this routing.
One thing though, any box on this subnet would not be able to access the
Internet without NAT or IP masquerading. You can do NAT / IP
masquerading with a Linux box, modern router or something similar.
Darryl Bond
>
> [EMAIL PROTECTED] on 09/27/2000 10:33:23 AM
>
> Please respond to Foxboro DCS Mail List
> <[EMAIL PROTECTED]>
>
> To: [EMAIL PROTECTED]
> cc:
>
> Subject: Re: DHCP for Solaris v2.5.1?
>
> On Wed, 27 September 2000, [EMAIL PROTECTED] wrote:
>
> > Is anyone using DHCP with an AW51 running Solaris v2.5.1? I
> > know Foxboro doesn't offer it, but I have seen 3rd party s/w
> > that provides it for v2.5.1. We have been using DNS w/o
> > support since I/A v4.1.1 on AW51As and Bs. I don't have to
> > have DHCP, but find myself spending more time than I would
> > like justifying my requirement for static addressing to
> > TELCOM, IT and others.
>
> Hi Jim,
>
> What are you looking to accomplish? Are you talking about having static
> IP address for your Sun boxes? or static IP for your PC so the Sun
> boxes can recognize it reliably?
>
> To answer your questions directly: No, we don't run DHCP or DNS on our
> Sun boxes. We rely on the corporate IT people to maintain their DNS
> servers properly. We then set up our Sun boxes to first look in the
> local hosts file, then reference the remote DNS server(s) for
> communications out of the 2nd Ethernet port. There are a slew of
> configuration that you need to do to achieve this. It's not
> difficult, but not trivial either. There was a discussion on this subject
> a few months back. You can try searching the archive
> (http://forums.invensys.com/suites/dispatch.exe/Foxboro_DCS_Mail_List).
>
> Regards,
>
> Duc M. Do
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
