Problems with FVS318v3

[darkreader]

I have the latest firmware and have even restarted the router. There is one computer and a printer with a static IP that is hooked to a switch which is going to the router. I'm not sure if this is causing a problem. All computers are using DHCP. This includes DNS and gateway information. The printer is using 192.168.0.10. There is no VLAN configured nor is there DynDNS.

The IP address lease 192.168.0.6 for the Network Card with network address 0019DBB76xxx has been denied by the DHCP server 0.0.0.0 (The DHCP Server sent a DHCPNACK message).

The system detected an address conflict for IP address 192.168.0.2 with the system having network hardware address 00:A0:C9:xx:94:xx. Network operations on this system may be disrupted as a result.

The IP address lease 192.168.0.2 for the Network Card with network address 0019DBB06xxx has been denied by the DHCP server 0.0.0.0 (The DHCP Server sent a DHCPNACK message).

Doing an ipconfig /release and /renew gives me the same IP address. DHCP scope on the router is 192.168.0.2 - 192.168.0.51 with a mask of 255.255.255.0.

I do have a personal firewall on this machine.

[jmizoguchi]

go back to previous one.

I had clients location act up with latest firm where quickbooks was not working every so often and was causing server and client pc to act up.

I had another client with same router with previous firm with same quickbooks server in same network design and never had issue

I revert one back on firm and fix the issue.. running fine for month now

I was going to ope the case about his myself. there is issue in firm

[JerryIrons]

I've had problems myself with dhcpnack and have a workaround if it helps anyone else. The problem I believe is a timing issue on the firmware. If you open a command prompt, do an ipconfig /renew you will get an access denied error. ipconfig /renew again and it works fine. Also if you do an ipconfig /release followed by ipconfig /renew it works fine. Problem is that the dhcp maximum is 24 hours, and when the client workstation tries to renew its ip address, it will throw a dhcpnack event in the event log, and any current tcp sessions are interrupted, which was playing havoc in some of my business applications. Eventually the workstation does pick up an ip address, but the damage has been done. Anyway the workaround:
Allow the workstation to pick up an ip via dhcp. Then go into the router and add this ip as a reserved ip. (you can get all info via the attached devices).
Somewhat tedious but it works. I am running the latest firmware by the way. You can also of course make ips static which will work. Hope this helps,

-Jerry

[jmizoguchi]

I think that is about valid fixes I agree too. looks like regular sharing from the server didn't effect this but only on certain app like you were saying. Not sure how the quickbooks works when IP issue happens. must say they only go back IP not pc names.

in my case it would cause issue few time a day so dhcp release of 24hrs may not quite fit my case.

[ebozzz]

Originally Posted by JerryIrons

Allow the workstation to pick up an ip via dhcp. Then go into the router and add this ip as a reserved ip. (you can get all info via the attached devices).
Somewhat tedious but it works. I am running the latest firmware by the way. You can also of course make ips static which will work. Hope this helps,

-Jerry

It will also be important to remove the reserved IPs from the randge of IPs being used for DHCP once they are assigned. If not there could be some IP conflict issues.

[jmizoguchi]

Originally Posted by ebozzz

It will also be important to remove the reserved IPs from the randge of IPs being used for DHCP once they are assigned. If not there could be some IP conflict issues.

I dont not use reserve IP within the DHCP range and I was getting the issue

[ebozzz]

Originally Posted by jmizoguchi

I dont not use reserve IP within the DHCP range and I was getting the issue

You were getting IP conflicts from standard DHCP assignments or were you referring to something else?

[jmizoguchi]

with the issue on latest firmware that causes some issue was not related to wether the PC was static ip within DHCP range or outside did not make any differences. some to do with DHCP on router after this firmware upgrade to latest.

lowering did not behave like latest firm did..

[ebozzz]

I understand now. Thanks for clearing that up. In my initial post I was just simply stating that the reserved IP, if used, would need to outside of the DHCP range. I'll stay out of the deeper issues because you guys have that covered.