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!

Very strange IP config!

Status
Not open for further replies.

gstar1703

IS-IT--Management
Apr 7, 2005
138
GB
Hi,
I have 2 windows 2003 servers & 70 Xp pro clients. 1 server is the DC,DHCP & DNS server whilst the other is a preinstalled NAS device. The NAS server has an internal IP address assigned to its only NIC and can be accessed using this IP. However when I run any IP monitors or even try to ping it, it returns the IP of 82.165.55.163! To complicate matters futher my FireWALL keeps catching outgoing traffic on port 80 to this IP...
How strange is this...?

FYI, the NAS is in our old NT4 domain which has full trusts setup with the 2003 domain -

Heres a ping -
Pinging nas.co.uk [82.165.55.163] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 82.165.55.163:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 
Are you sure that this IP address is not coming from Internet DNS? The domain name is registered and it might be resolving to that instead of anything local?

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
make sure the nas device is added to your DNS server.
 
Hi & thanx for your answers -
daveh777 - The NAS server is already added to DNS, forward & reverse entries.

TheLad - 82.165.55.163 is the IP of What I cant work out is why it's being resolved to that address instead of the local one?? Surely it searches local DNS for entries first?

Cheers
 
flush you dns cash and server dns cash.

Lars

Network admin for worldwide freight forwarders company.
mcp mcsa\: Messaging mcse -2003
 
Hi Lars,
Have done that also. I managed to fix it by flusing out Wins on the NT4 box. I then installed Wins on the 2003 server and stopped it on the NT4 box... Seems to have worked although I havent any entries in the new WINS server apart from itself as yet!

Should I be seeing XP machines turning up in WINS on the 2003 box?

Cheers
 
xp is using dns dont realy know if its still advertising itsself to wins, it should be for nt4 clients finding xp.

Lars

Network admin for worldwide freight forwarders company.
mcp mcsa\: Messaging mcse -2003
 
on your machine do an "ipconfig /flushdns", you may have cached the incorrect DNS entry before you added the nas to your DNS server.
 
Thanx to all for your help.
I have now updated DHCP settings on the server to point at itself for WINS also, which seems to have done the trick. XP clients are now registering in WINS & NAS has its own IP back - Another happy ending!
Cheers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top