| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 38887 | 2003-10-21 04:41:00 | Storing Computer Names and IP Address | sleepingsnail (4759) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 185377 | 2003-10-21 04:41:00 | Peer to Peer network using Windows 2000 SP4. All computers set to obtain IP address automatically and DNS Server address automatically. All computers have unique names but when I try to connect to one of them, and only that computer, I recieve an error message notifing me that there is a duplicate name. If I ping the computer with its IP address the ping comes back fine, but if I ping it using its name then the IP address that is pinged is the IP address of a different computer. Now I can fix the problem by manually assigning the IP address's but this problem only began after the following event. Our internet connection went down, even though the DSL router indicated that the connection was good, the router was replaced. This did not help and the original router replaced. The problem was solved by Telecom changing a configeration file at there end. My question is: is there a file that holds the information Name Admin IP address 15.108.5.3 Name Dispatch IP address 15.108.5.4 etc for the other computers so that when the command ping Dispatch is executed the name Dispatch is resolved to 15.108.5.4 I have checked likely files like host and networks, but not on all the computers, without finding any answers. Regards SleepingSnail The ADSL router is connected to a network hub/switch to which the other computer are attatched to. |
sleepingsnail (4759) | ||
| 185378 | 2003-10-21 04:57:00 | A hosts file is manually generated, so shouldn't be the problem. However each computer will cache addresses as it gets them (by asking the DNS server ...). The cache will time out to avoid invalid entries... but I suppose it could be set for too long a time. They should be cleared when each computer is started up, too. Try the arp command. If it exists in youir version of windows ... :D ... try it with "/?" first to find the options. e.g. "arp -a" will (probably) tell you what "this" computer knows about the network. |
Graham L (2) | ||
| 185379 | 2003-10-23 19:23:00 | Thanks Graham. Located the problem while experimenting with "arp" | sleepingsnail (4759) | ||
| 1 | |||||