Solved Hostname is resolving the wrong IP address

August 31, 2012 at 09:22:31
Specs: Windows 2008r2

Hello All,

First off I should say that I am in a educational environment I am the system admin at the school. I am having trouble with getting a copier that I have networked to stay registered in the system. When connecting all the equipment back for the new year I was having trouble getting this one specific copier back online properly.

I used to have it assigned with a static IP because the person that was here before me had all the computers map the printer using the IP instead of Hostname but that was causing IP conflicts so I removed it and mapped the printer through Hostname which is made "MPF-TOSHRM328"

So now for the actual problem, after the copier got the new dynamic IP of 10.8.214.151 i thought it would be fine and everything would click in because it was mapped to the host name and not the IP. But when I do a tracert on the hostname it still shows up with the old IP. and now that the old ip has been reassigned it actually points to a physical machine now. Weird. All attempts to flush the DNS have not resolved the issue. I even tried going in and deleting the entries in manually. No luck. As a point of reference here is the result from the tracert.

Tracing route to MFP-TOSHRM328.78B450.nycboe.org [10.8.214.126]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SLS330W09 [10.8.214.126]

Trace complete.

Thanks in advance for any help.

I should also mention that this server is only here in the sense that it is the DC for the computers on this floor. There is a whole other system that assigns the IP's and handles the DNS. I do not have access to it, it is run by the main network people at the central offices.


See More: Hostname is resolving the wrong IP address

Report •


✔ Best Answer
September 12, 2012 at 15:29:58

print by ip address not host name and your issue is solved. No dns /name resolution required.

\\ipaddress\printersharename

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's



#1
August 31, 2012 at 10:15:59

You could do worse than talk to those other people.

Report •

#2
August 31, 2012 at 10:20:58

I used to have it assigned with a static IP because the person that was here before me had all the computers map the printer using the IP instead of Hostname but that was causing IP conflicts

I would have started by investigating the duplicate IP issue before doing anything else. A dupe IP isn't really the same thing as something being broken and can usually be quite easily fixed. For instance, had you checked and discovered the IP assigned to said printer was in the DHCP scope, you could have excluded or reserved that IP and the issue would have gone away.

Alternatively, you could have given the printer an IP outside of your DHCP scope if your entire subnet wasn't included within that scope. In a larger environment, the exclusion/reservation would likely be the better idea in the long run.

so I removed it and mapped the printer through Hostname which is made "MPF-TOSHRM328"

While printers is not my department here where I work, I do know we use print servers and the actual IP, not the hostname, to map printers to clients. Using the hostname requires a DNS whereas the IP is direct and removes potential DNS issues.

My recommendation is you statically assign and IP to the printer. As mentioned above, use a reservation/exclusion, or an IP outside your DHCP scope, and see if that doesn't fix the issue. I suspect it will. You will of course have to delete the existing printer and reinstall it on all clients after you change it to a static IP.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#3
August 31, 2012 at 11:08:55

Thanks for your response, the copier is setup using the print server and pushed using GP, sorry I didn't mention that. While I appreciate your suggestion I would rather try and keep it setup though hostname as I don't have access to how DHCP gives out its addresses I only manage the DC that the computers on my floor are joined to. The other floors are different schools. Basically I just want to know how to reset the IP that it keeps assigning it. When I ping the hostname it automatically pings the old IP that has already been reassigned to another computer. How can I force the system to refresh the address ?

This is what It looks like when I ping and tracert:

C:\Users\Administrator>tracert MFP-TOSHRM328

Tracing route to MFP-TOSHRM328.78B450.nycboe.org [10.8.214.126]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SLS330W09 [10.8.214.126]

Trace complete.

C:\Users\Administrator>ping MFP-TOSHRM328

Pinging MFP-TOSHRM328.78B450.nycboe.org [10.8.214.126] with 32 bytes of data:
Reply from 10.8.214.126: bytes=32 time<1ms TTL=128
Reply from 10.8.214.126: bytes=32 time<1ms TTL=128
Reply from 10.8.214.126: bytes=32 time<1ms TTL=128
Reply from 10.8.214.126: bytes=32 time<1ms TTL=128

Ping statistics for 10.8.214.126:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Other than that, how would I go about assigning it an IP outside of the scope? If this issue cannot be resolved though hostname ?


Report •

Related Solutions

#4
August 31, 2012 at 11:23:11

Your server isn't running the dhcp server? Ips coming from the router then?
Lets see a ipconfig /all from one of your workstations for review.

Host name is a issue of DNS. This is corrected by correcting the static dns host and ptr records.

Where is your dns server?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#5
August 31, 2012 at 12:26:11

This is off the server:

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : 78B450DC01
Primary Dns Suffix . . . . . . . : slssrv.78b450.nycboe.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 78B450.nycboe.org
schools.nyc.gov

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client) #35
Physical Address. . . . . . . . . : D4-AE-52-78-66-05
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.8.214.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.8.214.1
DNS Servers . . . . . . . . . . . : 10.8.214.5
Primary WINS Server . . . . . . . : 10.8.208.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{2FD161BE-D6C3-4B1D-AE3F-C121C27A98C5}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

This is off a workstation :

H:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SLS330W17
Primary Dns Suffix . . . . . . . : slssrv.78b450.nycboe.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : slssrv.78b450.nycboe.org
78B450.nycboe.org

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : 78B450.nycboe.org
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 18-A9-05-30-1A-FB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4548:57fa:51b1:823a%15(Preferred)
IPv4 Address. . . . . . . . . . . : 10.8.214.143(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, August 30, 2012 2:24:17 PM
Lease Expires . . . . . . . . . . : Friday, September 07, 2012 2:24:16 PM
Default Gateway . . . . . . . . . : 10.8.214.1
DHCP Server . . . . . . . . . . . : 10.8.208.100
DHCPv6 IAID . . . . . . . . . . . : 303606021
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-6A-25-5D-18-A9-05-30-1A-FB

DNS Servers . . . . . . . . . . . : 10.8.214.10
10.251.54.21
10.251.54.22
Primary WINS Server . . . . . . . : 10.8.208.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.78B450.nycboe.org:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : 78B450.nycboe.org
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 14:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

As to your question of where are the IP's coming from, they come from the massive MDF room which is managed my the network people at the central office, I only manage one school, of the 3 that are in the building. The server that I manage is only used as a DC/printer/file server for the floor. There are things hooked up in that room that I'm not going to even pretend I know whats going on in there, I mean eventually I would like to start learning but I am young in my enterprise networking skills at the moment.


Report •

#6
August 31, 2012 at 12:53:04

You say another system handles DHCP and DNS. If you are having DNS resolution issues you need to talk to the people managing the DNS server. Sounds like there is a rogue "A" record on the DNS server that needs to be deleted.

Have you tried doing an "nslookup" to check whether the problem is somehow with the workstations (very unlikely) or with the DNS server?


Report •

#7
August 31, 2012 at 15:19:09

server
DNS Servers . . . . . . . . . . . : 10.8.214.5
wkst
DNS Servers . . . . . . . . . . . : 10.8.214.10

Appears someone is confused as to which is the correct dns server. If you have two both should be listed on both.

You will need to either correct your servers dns ip or call the tech folks and have them correct their dns entry to point to your correct ip dns server.

In other words either your servers dns pointer is wrong or the dhcp servers dns pointer is wrong.

Once you can correct. The other they need to correct. But first which is wrong?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#8
September 12, 2012 at 06:41:21

yea, so i think over the summer they changed the configuration in the building, the correct DNS server is the .5 one.

The issue actually resolved itself, it's just that it take the system a very very long time to update the fact that the machine has a new ip. Once I stopped messing with iteverything balanced out overnight. Even though the problem is fixed I fear that it will come back eventually because it' no a true fix, if the machine looses power or something it will grab a new IP and then it will take a while for the system to reflect that the hostname is linked to a new IP. Meanwhile, all the jobs that go to that printer are being rejected caus they're going to the wrong ip linked to the hostname.


Report •

#9
September 12, 2012 at 15:29:58
✔ Best Answer

print by ip address not host name and your issue is solved. No dns /name resolution required.

\\ipaddress\printersharename

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •


Ask Question