Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 275
  • Last Modified:

Not getting DHCP IP from Server

I have a network that is using DCHP to assign IPs. I want to take out a computer and replace it with a thin client. The computer receives an IP address just fine but the thin client will not. If I use the thin client in a different area, it works just fine. The only thing that works, is the computer and as far as I can see there isn't anything special setup on the computer that it will be different than the thin client. Any ideas?
0
itadminnek
Asked:
itadminnek
  • 5
  • 3
1 Solution
 
CompProbSolvCommented:
Is there any chance you have run out of IP addresses in the pool on the DHCP server?

What is the device that is the DHCP server?
0
 
itadminnekAuthor Commented:
No there is still IPs left and I am running SBS 2003
0
 
baraneCommented:
Barani:

Have you tested  more than one thin client with port.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
itadminnekAuthor Commented:
Yes and they do not work either only the computer works
0
 
CompProbSolvCommented:
Can you set up a static IP address on the thin client to make sure this is really a DHCP issue and not a general connectivity issue?
0
 
itadminnekAuthor Commented:
I did give the thin client a static IP, still no luck.
0
 
CompProbSolvCommented:
If you experience the same problem with a static IP, then this is not a DHCP issue.  There is a more basic networking issue.

I'd be looking as issues such as speed (10/100/1G), duplex (half/full), and wiring.  The speed and duplex are typically set to automatic, but I'd try setting 10M half-duplex just to see if that rectifies the issue.

Although you have indicated that a computer works at the same location (using the same cable, I presume), there may be an issue with wiring.  Most computers will automatically switch the receive and transmit pairs if they are connected to a port that is wired the "wrong" way; the terminal may not.  Granted, it would be odd for this circumstance, but we have to look for odd things sometimes!

If the LED at BOTH ends of the network cable (one at the switch or hub, the other at the terminal) are illuminated, the wiring is probably correct.

Is there any chance you have some fancy switch that restricts that port based on MAC address?
0
 
itadminnekAuthor Commented:
I think it is the switch, it is very old and I think either the ports are bad on it. I have a new on order to replace it, so for now I am going to end this question and open a new one if the problem is still there. Thanks for all the help!
0
 
itadminnekAuthor Commented:
The question was not completly answer due to ordering of new parts.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now