Minor Issue with adding a New Box to Workgroup

[Ol Bob]

I just completed a new core2duo box running xp-sp2. When it was joined to the workgroup all seemed well and I was able to update it and also see all other boxes and share files and ect.When veiwing all workgroup computers the name of this new one is visable and correct.However its client name in my Linksys rv-082 dhcp chart shows as "new-client" only, not the computer/client name as the rest do. Further, when the box is first booted up it will show up in dhcp multiple times listed as New-host 2 and new-host 5 ect, all with the same and correct Mac address but with multiple different IP addresses.I am using the Intel Pro-1000 Mt nic with the latest drivers.Why would this box not show up under its windows computer name in the dhcp client table, is this a windows problem or something with the rv-082?What should I be looking for to fix this issue that's making me crazy?Could this be some kind of spyware or virus?

 

[Ol Bob]

Any one want to even try a guess?

 

[mxnerd]

Shutdown every computers on the net including Linksys rv-082. Wait 5-10 minutes and power back on, see if it fixed the problem.

Sometimes equipments just go crazy. I don't think it has anything to do with virus or spyware.

 

[p0lar]

Originally posted by: mxnerd
Shutdown every computers on the net including Linksys rv-082. Wait 5-10 minutes and power back on, see if it fixed the problem.

Sometimes equipments just go crazy. I don't think it has anything to do with virus or spyware.

And the next time it happens, what do you do? Shut everything down again and hope when it powers back on that all the problems are tucked away in Mickey Mouse's Disney pocket, never to be seen again?

 

[mxnerd]

I'm trying to help. If you know the answer and can help, why don't you say it?

 

[mxnerd]

Originally posted by: p0lar

And the next time it happens, what do you do? Shut everything down again and hope when it powers back on that all the problems are tucked away in Mickey Mouse's Disney pocket, never to be seen again?

Base on what you assume I'll do the same thing next time? Ol Bob probably has less than 5 computers, shutting down everything is easy and does no harm, why can't he do it?

It could be DHCP service malfunctioned, he can stop the service and restart it, and go to the computer and use IPCONFIG /release and IPCONFIG /renew command to reget IP.

Or it could be other problem. I might not have the expertise as you, but I'm trying to help. If you know the answer and can help, why don't you say it instead insulting people?

 

[p0lar]

Originally posted by: mxnerd
Base on what you assume I'll do the same thing next time? Ol Bob probably has less than 5 computers, shutting down everything is easy and does no harm, why can't he do it?

It could be DHCP service malfunctioned, he can stop the service and restart it, and go to the computer and use IPCONFIG /release and IPCONFIG /renew command to reget IP.

Or it could be other problem. I might not have the expertise as you, but I'm trying to help. If you know the answer and can help, why don't you say it instead insulting people?

Calme toi, don't get your shorts in a bunch because there's no insult or personal attack there. I'm only criticizing the reboot it because you're not sure what's wrong method. Whether you invented it or not is irrelevant, it's not a proper solution to any problem.

Also, note that I make no claim in ANY direction that I can service anything Windows-related.

 

[cleverhandle]

Originally posted by: Ol Bob
When viewing all workgroup computers the name of this new one is visable and correct.However its client name in my Linksys rv-082 dhcp chart shows as "new-client" only, not the computer/client name as the rest do.

The DHCP protocol doesn't require that a client send a hostname to the server. In fact, if sent, this information is usually ignored outside of fairly sophisticated networks. So the fact that the name is missing isn't really anything to worry about. If you want to poke around at it, check out the client settings for the computer name and for the TCP/IP properties and see if there's anything there about "sending a hostname to the DHCP server" or similar. I don't do much with windows, so I'm not sure where that will be off the top of my head.

Further, when the box is first booted up it will show up in dhcp multiple times listed as New-host 2 and new-host 5 ect, all with the same and correct Mac address but with multiple different IP addresses.

Now that is kind of strange. Usually when a DHCP client starts up it sends a DHCP request with a smallish timeout. If it doesn't get a reply, it sends another request with a longer timeout, and repeats this several times before it gives up. It could be that, for some reason, the PC is sending several requests even though the first one is being responded to already. Not sure why it would do that, though. If there's anything between the PC and the DHCP server (switches, packet filters, etc.), you might try hooking the PC directly to the DHCP server and see if that changes anything. Might also be worth trying another cat5 cable. I guess it could be related to the NIC or drivers, too. You could try out another card. But if anything, I'd probably peg it as a bug with the Linksys that's only showing up with this particular combination of hardware.

Could this be some kind of spyware or virus?

Extremely unlikely. What good would making a DHCP request do for malware? The PC already has connectivity.

What should I be looking for to fix this issue that's making me crazy?

Some valium, perhaps? Really, if everything works OK, getting hungup about a duplicate entry in your router's status screen seems a little silly to me. I understand the desire to have everything look and work exactly as you want, but modern networks, even simple ones, are composed of lots of moving parts from lots of different manufacturers. Sometimes one piece just doesn't quite fit the way you want it to. If everything functions properly you can let the aesthetics slide a bit.

 

[mxnerd]

And look at the event viewer in that particular PC, see if it gives you any error regarding networking. It probably will help debugging the problem.

 

[wirelessenabled]

Originally posted by: p0lar

Originally posted by: mxnerd
Base on what you assume I'll do the same thing next time? Ol Bob probably has less than 5 computers, shutting down everything is easy and does no harm, why can't he do it?

It could be DHCP service malfunctioned, he can stop the service and restart it, and go to the computer and use IPCONFIG /release and IPCONFIG /renew command to reget IP.

Or it could be other problem. I might not have the expertise as you, but I'm trying to help. If you know the answer and can help, why don't you say it instead insulting people?

Calme toi, don't get your shorts in a bunch because there's no insult or personal attack there. I'm only criticizing the reboot it because you're not sure what's wrong method. Whether you invented it or not is irrelevant, it's not a proper solution to any problem.

Also, note that I make no claim in ANY direction that I can service anything Windows-related.

If a reboot fixes the problem and you only need to do at an acceptable interval I would count it as a proper solution. Way better than spending hundreds of hours/days/months finding, or not finding, the obscure "real" cause.

In my case I reboot the HPUX servers I am in charge of every night whether they need it or not. Keeps lots of obscure problems from appearing.

 

[Ol Bob]

a quick update, problem still present. I shut down/.powered down everything and it made no difference.all 10 boxes and the file server came back up and were reconised by the rv082 by their windows name except this one.Its still just new host with 2 IP addresses assigned to the same MAC.I figured it must be a windows problem so I reformatted and reinstalled everything but that had no effect either. Thinking now it has to be something with the intel 1000mt nic but that seems to work ok otherwise.This home workgroup connects into a linksys switch, sr216, and the rv082 router is the dhcp server and internet gateway, not the network swith. Tho moving this box to different ports didn't help I have ordered a new switch, linksys sr 2016 gigabit model, as well as anouther 1000mt nic so the process of elimination is ongoing.

 

[Nothinman]

In my case I reboot the HPUX servers I am in charge of every night whether they need it or not. Keeps lots of obscure problems from appearing.

Man am I glad that I don't work with you...

Thinking now it has to be something with the intel 1000mt nic but that seems to work ok otherwise.This home workgroup connects into a linksys switch, sr216, and the rv082 router is the dhcp server and internet gateway, not the network swith. Tho moving this box to different ports didn't help I have ordered a new switch, linksys sr 2016 gigabit model, as well as anouther 1000mt nic so the process of elimination is ongoing.

If you can find a way to get a packet capture during bootup/DHCP release/renew that might help you see what's wrong.

 

[mxnerd]

First, did you connect all machines to SR216, then uplink SR216 to rv082? If yes, probably the particular port on SR216 that you connected for the machine malfunctioned. Change it to another port and see.

Second, try update rv082's to newest firmware and see if it fixes the problem. Third, use another brand / model of NIC on this machine and see if that fixes it.

And, do you have some special programs running on the machine?

Nothinman's method is also legitimate.

 

[nweaver]

it could be PXE booting during bootup, but if the DHCP server is assigning multiple IP's to the same MAC, I would guess it's a DHCP server problem.

 

[Ol Bob]

The rv082 being the DHCP server, why would it be doing this on only one computer rather than all of them?I'll check on PXE, that boot prompt comes up every time but i've never messed with it or even looked at it.Other boxes here use the same model nic and I've never had to fool with that on those but maybe its something in the oem flash.