Jump to content

Recommended Posts

Posted

Hi,

 

sorry if this is the wrong place and I don't make much sense but I am a bit confused and my network manager is away for the week and unfortunately I'm not that clued up in this department, so here goes...

 

We have just returned from easter break, our network worked fine on Friday just gone but coming in this morning there are a few issues:

 

1) staff are not able to log in on certain computers, when logging in locally I can see the network icon in the sys tray is 'aquiring a network address' which it fails to do so.

2) 1 or 2 machines have 'limited or no connectivity' a result of timing out I expect

2) certain phones were not working (no dial tone)

3) wireless is not connecting

 

I reset the switches on our main comms which kicked the phones back into life once they were reset also

 

I noticed that our wireless which is broadcast on a VLAN 600 is now kicking out a VLAN50, I found this by the IP address I recieved on my iPhone

 

I have restarted both of our DHCP servers which has done nothing.

 

I checked the event logs on an effected PC and got an Event ID 1002 with the following error:

"The IP address lease %1 for the network adapter with MAC address %2 has been denied by the DHCP server %3 (The DHCP server sent a DHCPNACK message)."

My co-worker tried to do a /release /renew on an effect PC and go an access denied error, I also tried this on another machine and did not recieve the error but it timed out and gave me the following error:

"An error occured while renewing interface Local Area Connection: Unable to contact DHCP Sever, request timed out."

 

I have checked VLANs of affected machines against VLANs of working machines and nothing has been changed, one of the PCs is in the same room as 2 others that work and all feed back to the same switch, this is the same in a few areas across site on different switches.

 

Sorry if this doesn't seem like a question but I am looking for some pointers or places to look, I am happy to gather more information if anyone thinks they may be able to help me out, unfortunately I cannot contact my manager as they are away on a course and I think I will only be able to get them after I will have left.

 

Thanks in advance for anything anyone can do.

Posted
We did have 1 actually yeah, not sure under which scope off the top of my head but can check tomorrow. What does this mean?
Posted
We did have 1 actually yeah, not sure under which scope off the top of my head but can check tomorrow. What does this mean?

There may be other circumstances, but it is allocated when DHCP detects an IP address clash on that address.

 

Your mentioning of DCHPNAK responses reminded me of an issue we had where DHCP caused a broadcast storm due to an IP clash with an IP address which had been reserved in DHCP. Now I look back at my notes, I am not sure it is relevant unless the BAD_ADDRESS flag has appeared on a reservation entry - rather than just a regular lease.

 

If you have several DHCP servers on the same VLAN and subnet, it might be worth disabling all but one of them to see if that has any effect.

Posted

Well this morning the BAD_ADDRESS was not visible in any of the scopes, I think it was under a lease and not a reservation. After doing loads of testing and just finding data it seems it may have come down to something quite simple. During the first week of the Easter holidays our switches and cabs were moved into 2 new cabs, speaking to the ICT Services today, it sounds like things may not have been plugged back in the correct places. DOH!

 

As above, I don't usually deal with these kinds of things and we fall short from time to time on labelling and documentation so I had not picked up on this. We have someone dialled in are hopefully on our way to a fix.

 

I'll keep the thread updated just incase anyone comes across similar problems but hopefully not everyone is as daft as we can be... not all the time, just sometimes.;)

Posted

Finally got this sorted yesterday, well working but not fully resolved.

Seems we have a cross over somewhere on the network between a VLAN 600 and a VLAN 50. When looking through DHCP scopes, computers that were actually tracked back to being patched into a VLAN50 port were kicking out the wrong IP address, our wireless was also kicking out a VLAN50 address when it should be VLAN600. Disabling the V600 scope bought everything back online, we did this a couple of times and it broke and started working again each time. We currently have our Trapeze unit turned on casting out a V50 which is fine as laptops can use that correctly. I have decided to keep the V600 scope disabled until Monday when my manager returns so that they can decide how to track it back.

Posted
Clearly not. Unfortunately I'm not the most clued up in this area and haven't had much experience with the network side of things. My role is more user/hardware/software. Although I have wanted to learn a lot more about networking and hope that having had this problem whilst the two networking people were away will help me push for training.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...