Hugh,
This has been a pretty long thread, maybe we should get a little more data
in one place, to chase down the problem? You may have stated all this
before but maybe it'd be worth summarizing in one message:
- What router are you running?
- Does your router have sufficient logging to list when it receives and
responds to DHCP requests? (ie, a log of time/date when it sends out
a new IP address to a particular NIC)
- What server OS (and patch level) is your ftp server running?
- When you said a while back you changed the mobo on the ftp server, did
you move the old NIC card over, or are you using the onboard NIC of
the new mobo? (this is important to know, if one suspects misbehavior
of the NIC card)
- Would you please paste the output of IPCONFIG /ALL, run from a command
window (on your presumably Windows based) ftp server?
Now for some nitty gritty:
If the server's IP address is getting changed, let's postulate why that
might happen:
1. perhaps the cable/connector has gone bad, and the rotuer sees some
disruption and for some reason decides to renew the IP binding.
2. the router may have built in expiration setting, and when reached
gives out new IP addresses. (on my router, I have "permanent
assignment" enabled, so it never reuses IP addresses assigned to
a given MAC address. Makes network debugging easier, but the
laptops stay dynamic from their point of view).
3. the server detects a loss connection (due to bad cable/NIC), and
requests a new address.
Note that I don't think exactly #1 or #3 can occur quite as stated, but
it is important to start thinking about _why_ a new address would get
assigned. A few things that can happen that may cloud the picture:
- you inadvertently permanently assigned an IP address to another computer
besides your ftp server, and the router sees two MAC addresses with the
same IP.
- you somehow missassigned (by typo) the gateway address used by your
server, and it ends up on a different subnet, which you happen to
have left a wireless access point open on (or another router), and
_it_ is handing out addresses on _that_ subnet, but the addresses
are close and you didn't notice (as in 192.168.2 instead fo 192.168.0).
- you've enabled MAC masquerading in your NIC somehow, maybe through
software, thus your MAC address for the ftp server is different than
you think it is, or worse, is changing.
- you changed NIC's when you went from the old mobo to the new one,
but didn't change the MAC address -> static IP address binding in
the router.
Anyway, to chase down some of this, take a careful look at your
router's log, and see when it decided to assign an IP address
to what MAC address. Take a careful look at those MAC addresses
and make sure there are no duplicates, and that your server's
MAC address isn't changing, and that you've properly entered
its MAC address into your router's static IP assignment table.
Back to static IP's. The way I assign them, is in the network
adaptor's TCP/IP properties. I click "Use the following address"
on the General tab, and plug in the gateway and mask as well.
IPCONFIG reports the following:
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010
PCI
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : [obscured]
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
My server is hardwired to .100, which is outside the dynamic IP range
on my router.
--
----------------------------------------
To Change your email Address for this list, send the following message:
CHANGE WIN-HOME your_old_address your_new_address
to: [EMAIL PROTECTED]
Note carefully that both old and new addresses are required.
