the things that happen when a man is sleepy... well you guys get the idea... the point being... you can tell if the host name is connecting to the ip address... or not...
and yes its dns not dhcp... my appologies for mixing my terms...
also yep... if you get a 169.xxx.xxx.xxx address that usually means dhcp is down...
sorry about that...
just got up...
and reread my junk...
made the correction in the original post...
let me know if all is well...
I am never a man averse to learning or correction...
Sad To Say I Don't Have a Life
I do this stuff on the weekends too
Sad To Say I Don't Have a Life
I do this stuff on the weekends too
Don't worry about it. You, along with others, have taught me so much. A few weeks ago I wouldn't have even caught that mistake. This is no longer about only networking a copier for me. I want to know much more and I want to know how to troubleshoot DHCP and DNS. At the heart of IT it's about solving problems and you have to have a deep understanding of this stuff to find and correct the problem. Right?
Here's a question for the IT experts on here:
Lets say I suspect that a virus (or something else) is assigning rouge IP address and I want to find out if there's a duplicate IP address. What's the best way to see if there's a duplicate IP address. I know one way is to use a scan tool. I used NetScan Tools Pro and ran an ARP request for the copier IP address. It sent out an ARP request and showed every MAC addresses that's on that IP address. So that's one way. But that's an invasive method and I would need to get permission to run something like that on a customer's network.
Are there any less invasive ways to do this?
A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
Blessed are they who can laugh at themselves, for they shall never cease to be amused.
I don't reply to private messages from end users.
Bookmarks