[AccessD] dhcp stuff

Jim,

I do not have any computer being the dhcp server simply because I did not
want to depend on a machine for that function, it might be down for repair
etc.   


John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Monday, December 18, 2006 3:15 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] dhcp stuff

Just a quick note... without reading through all the text and considering
that this issue may have already been commented on:

If the server has its own DNS/DHCP setup then the Router's auto-assignment
feature must be turned off. (Discovered that the hard way.)

HTH
Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Monday, December 18, 2006 5:48 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] dhcp stuff

Thanks Stuart for that link.

My question really had to do with the router rather than the machine,
although perhaps not.  I do not know how any of this works, however my
assumption was that if the router was set up to assign IP addresses (the
DHCP Server) and it had a table of static assignments which included both
NICs on that machine, then it would TELL each NIC what IP it had to use.  I
suppose if the router did indeed TELL both NICs what IP address to use, and
it told them to use the addresses in the static table, and one of the NICs
later came back and TOLD the router "I am using this address" then perhaps
the router would log that under "dynamically assigned".

Of course I haven't a clue how it really works, that is truly a WAG.

In the end, everything is working.  I was trying to get remote desktop
working on several of my machines on my network.  In order to do that, the
router has to do port forwarding.  In order to do that it has to know at all
times what IP address a given machine will be at, and so I went into the
router and created entries in the Static IP table for all the NICs on all
the machines.  In general that worked, except that on the lone machine that
has two NICs, one of the NICs ended up having an IP address in the Dynamic
IP address table in the Router, IN ADDITION TO the static address, and was
in fact using the Dynamic address.  In order to force that NIC to use the
STATIC address assigned in the Router, I went into properties for that NIC
and assigned it that STATIC address in the properties in Windows.  Now the
NIC does indeed use the Static address assigned by the router, if only
because I ordered Windows to do so in the properties for that NIC in
Windows.

Having all of that straightened out, I then did the port forwarding and
remote desktop magically started working again.

As for following Microsoft's recommendations on this and disabling one of
the NICs, I probably will, although if the IP addresses are Static and the
port never fails it probably doesn't matter.

NVIDIA is trying to lead the world into using dual NICs and having the
ability to "prioritize" packets sent through the two NICs.  Applications can
be specifically assigned to use a specific NIC, and then if there is data to
be sent on both NICs, one gets priority.  The idea is simple, the reality is
less so.  If I could make it work, I could do things like use one of my
machines to do Skye and upload data to my client.  Assign Skye to the high
priority channel and file transfers to the lower priority channel.  Then
Skye packets (going out) would have higher priority and people on the other
end of a Skye call would hear a higher quality signal if I happened to be
doing uploads at the same time.

Whether I will ever really use that is another question, especially
considering the resistance to such stuff from the OS vendor.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Sunday, December 17, 2006 3:09 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] dhcp stuff

Oops, forgot the URL
http://support.microsoft.com/kb/175767


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com