Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Stats Server will not connect with manual IP address

Status
Not open for further replies.

JonathanMortimer

IS-IT--Management
Sep 19, 2008
97
Hi,

We have a PowerEdge 4600 which we've just recently set up as a log stat server. It was working fine with a DHCP-assigned IP address of 192.168.46.5, but since changing it to a manual IP address of 192.168.46.251 the DHCP server just doesn't want to know. We've excluded the 46.251 address from distribution (same as our other servers which have fixed IP addresses, which all work fine), restarted the stat server (it doesn't do anything much during the day at the moment), but nothing seems to make a difference. It just sits their 'Acquiring network address' and eventually Windows tells us that there is a conflict with another machine on the network, but I'm fairly certain that there are no other machines on the network with the 46.251 address.

Erm, help please! :}
 
PS I can ping the 46.251 address just fine seemingly from any machine on the network.
 
With your server assigned the DHCP address that doesn't end in .251, does the .251 IP Address still ping?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------
 
Yes it does, and that's very puzzling. How can I find the machine with this .251 IP address? It doesn't show up in any network browsing I do, and isn't in the list of DHCP-assigned addresses.
 
You can perform a tracert to the IP address and depending on how your system is configured it might come back with a name via DNS?

Or you could try an MSTSC connection to see if it is a server that will give you an RDP connection?

Or you can see if you can manage it via Computer Management?

Or you can see if you can telnet to it?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------
 
Tracert output: 1 2ms 1ms 1ms 192.168.46.251

Cannot telnet (Connect failed);

Cannot Remote Desktop to it;

46.251 does not appear in any lists on the servers except in the 'Do not distribute' DHCP list, to the best of my knowledge.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top