Replies

By complete coincidence, I came across a VBS script that does the job and am posting for future reference.

You can find (and download) a script at http://www.billsway.com/vbspage/%5B/url%5D – look for the “Get IP Address” script. Note that all scripts on this site are copyrighted by Bill James and the usual disclaimers apply.

Cheers,

Final update to this post…

Our router manufacturer thinks it may be a firmware issue and has asked us to upgrade to the latest version. Due to an on-going desktop rollout, we will not be in a position to do this until the first quarter of next year – we have a “if it ain’t broke, don’t fix it” approach at the moment?!

I am now convinved this is a router issue and not related to Windows XPp or any other version of Windows OS.

Thanks to all those that helped.

Regards,

Final update to this post…

Our router manufacturer thinks it may be a firmware issue and has asked us to upgrade to the latest version. Due to an on-going desktop rollout, we will not be in a position to do this until the first quarter of next year – we have a “if it ain’t broke, don’t fix it” approach at the moment?!

I am now convinved this is a router issue and not related to Windows XPp or any other version of Windows OS.

Thanks to all those that helped.

Regards,

Hi!

We’ve always used DHCP on this LAN, but my predecssor elected not to implement DNS or WINS (?) – so we had a lot of Broadcast traffic flying around! (another story, but why would you do that?).

Non of our PC’s have HOSTS or LMHOSTS entries (I’ve checked already) and this error is repeatable on any PC in the LAN. DNS/WINS has been checked (including reverse DNS) and purged (see last post). Results of NETSH attached – everything as it should be.

I’m now convinced this has to be the router – will post update once I’ve spoken to the manufacturer.

Thanks for jumping in!

Cheers,

Hi!

We’ve always used DHCP on this LAN, but my predecssor elected not to implement DNS or WINS (?) – so we had a lot of Broadcast traffic flying around! (another story, but why would you do that?).

Non of our PC’s have HOSTS or LMHOSTS entries (I’ve checked already) and this error is repeatable on any PC in the LAN. DNS/WINS has been checked (including reverse DNS) and purged (see last post). Results of NETSH attached – everything as it should be.

I’m now convinced this has to be the router – will post update once I’ve spoken to the manufacturer.

Thanks for jumping in!

Cheers,

Hi,

You’re not the only one (that is stumped).

Powered off the PC that is using the offending address, deleted lease from DHCP, checked that both DNS servers had updated accordingly (OK) and deleted all entries from WINS server. Can no longer ping offending PC by name or IP (unsurprisingly). Peformed TRACERT (attached) and am still seeing first hop to 192.168.2.100! Arrgh!

This has to be the router – I’m on to the manufacturer now and will post outcome.

Many thanks for all your help and pointers,

Cheers,

Hi,

You’re not the only one (that is stumped).

Powered off the PC that is using the offending address, deleted lease from DHCP, checked that both DNS servers had updated accordingly (OK) and deleted all entries from WINS server. Can no longer ping offending PC by name or IP (unsurprisingly). Peformed TRACERT (attached) and am still seeing first hop to 192.168.2.100! Arrgh!

This has to be the router – I’m on to the manufacturer now and will post outcome.

Many thanks for all your help and pointers,

Cheers,

Completes in one hop, to the correct IP. As does TRACERT to mystery gateway address (attached).
All PC’s on local LAN can repeat this error.

Am beginning to think it must be a hard coded error in the gateway router?

Cheers,

Completes in one hop, to the correct IP. As does TRACERT to mystery gateway address (attached).
All PC’s on local LAN can repeat this error.

Am beginning to think it must be a hard coded error in the gateway router?

Cheers,

IPCONFIG shows the correct gateway (192.168.2.254) that isn’t being used. ROUTE PRINT shows the correct gateway also (attached). A TRACERT (attached also) still shows the first hop going to our old gateway address (192.168.2.100), which is now assigned (by DHCP) to one of our workstations.

(NB: In the TRACERT I’ve changed the FQDN of the first hop and the IP address of the second hop – paranoid ICT Manager!)

Thanks,

IPCONFIG shows the correct gateway (192.168.2.254) that isn’t being used. ROUTE PRINT shows the correct gateway also (attached). A TRACERT (attached also) still shows the first hop going to our old gateway address (192.168.2.100), which is now assigned (by DHCP) to one of our workstations.

(NB: In the TRACERT I’ve changed the FQDN of the first hop and the IP address of the second hop – paranoid ICT Manager!)

Thanks,

Sorry, should have said…

DHCP is assigning all our TCP/IP services and I’ve already checked for hard coded gateway. Have also renewed IP configuration many times too…makes no difference. I can recreate the problem on other PC’s in LAN.

Ade

Sorry, should have said…

DHCP is assigning all our TCP/IP services and I’ve already checked for hard coded gateway. Have also renewed IP configuration many times too…makes no difference. I can recreate the problem on other PC’s in LAN.

Ade

Thanks for that. Our templates are very basic and are without VBA coding at present – that’s the next project after the rollout!

Cheers,

Thanks for that. Our templates are very basic and are without VBA coding at present – that’s the next project after the rollout!

Cheers,