IPCONFIG /RENEW

Nov 19 03 10:37 am

I have been runing Wingate since it's early days.

Now when our ISP DHCP address lease is expired the network adapter can not renew the IP.

Anyone else having this Problem, or is it time to buy a Cisco Router.

Nov 20 03 9:43 am

I'm somewhat confused, so the problem is with the NIC correct? It won't release the old IP configuration? If that's the case, I would try removing the card from the System/Device Manager, then restarting your machine and allowing it too reinstall itself.

If you still have problems I would try another NIC before moving ahead to a Cisco router, which can be a pretty expensive solution...:)

Nov 20 03 9:47 am

I figured it out.

The Card is working fine (wingate's fire wall is attaching it's self to the TCP/IP stack) disabling the firewall service is one solutions

I created a program to

stoping wingate service
renew IP
Start wingate service

Everything works fine..

Nov 20 03 9:59 am

Very cool, I'll keep that in mind. :)

Jan 03 04 12:45 am

I'm Having the same problem. My Linksys router assigns IP address to my #1 NIC and I have to stop Wingate, renew my NIC, then start Wingate. Is there a fix in the works? Can you configure Wingate to let the router through to renew the NIC? Doesn't seem like you should have to write a batch file to let the router renew the NIC.

Jan 05 04 8:25 am

paul5 wrote:I'm Having the same problem. My Linksys router assigns IP address to my #1 NIC and I have to stop Wingate, renew my NIC, then start Wingate. Is there a fix in the works? Can you configure Wingate to let the router through to renew the NIC? Doesn't seem like you should have to write a batch file to let the router renew the NIC.

Does this mean you have a corresponding block message in the firewall ? (At the same time as the release/renew is happening)

Jan 13 04 9:40 am

When the lease expires on NIC#1 (connetion to the internet), Wingate won't allow my router to renew the lease. Error message from winipcfg states that DHCP Server is not available and the system assigns a new IP (169.xxx.xxx). Wingate then informs me that a new external interface has been detected.
I have tried a work-around with scheduler to stop all services, then a batch file does a release/renew. This has failed. The only way I can get a sucessful release/renew is to Stop Engine from taskbar, then release/renew. I did not have this problem with 5.1
Any thoughts or ideas would be appreciated.

Jan 13 04 10:17 am

paul5 wrote:When the lease expires on NIC#1 (connetion to the internet), Wingate won't allow my router to renew the lease. Error message from winipcfg states that DHCP Server is not available and the system assigns a new IP (169.xxx.xxx). Wingate then informs me that a new external interface has been detected.
I have tried a work-around with scheduler to stop all services, then a batch file does a release/renew. This has failed. The only way I can get a sucessful release/renew is to Stop Engine from taskbar, then release/renew. I did not have this problem with 5.1
Any thoughts or ideas would be appreciated.

This precisely describes one of the problems I've been having as identified in the 'DNS and disconnects remain issues' thread, right down to the assignment of the 169.xxx.... IP.

Dennis

Jan 13 04 10:29 am

When the lease expires on NIC#1 (connetion to the internet), Wingate won't allow my router to renew the lease. Error message from winipcfg states that DHCP Server is not available and the system assigns a new IP (169.xxx.xxx). Wingate then informs me that a new external interface has been detected.
I have tried a work-around with scheduler to stop all services, then a batch file does a release/renew. This has failed. The only way I can get a sucessful release/renew is to Stop Engine from taskbar, then release/renew. I did not have this problem with 5.1
Any thoughts or ideas would be appreciated.

Jan 13 04 2:34 pm

Aye, there was a problem in the driver. If you care to try the new driver, I can send the test build to you - just let me know what OS you are running.

Jan 13 04 2:57 pm

genie wrote:Aye, there was a problem in the driver. If you care to try the new driver, I can send the test build to you - just let me know what OS you are running.

Mine is Win98SE build 4.10.2222. Wonder if Paul5's is the same?

Thanks,
Dennis

Jan 13 04 3:22 pm

kalvos wrote:Mine is Win98SE build 4.10.2222. Wonder if Paul5's is the same?

The new driver solves this problem for me on Win98SE. Great work!

Dennis

Jan 13 04 3:24 pm

Cool - glad it fixed this problem!

Jan 13 04 10:38 pm

Mine is Win98SE build 4.10.2222, also. I'd love to have that new driver.

I'm not ready to give up 98 yet. (the devil you know.....) I'm waiting to see Win2000 in discount bins.... not thrilled with XP.