I have a Windows 2000 server installed in a VM partiton and it has two virtual apapters. The server name is "app01".
One adapter has a 10.0.0.x address and the other adapter has a Class A assigned IP address - we'll just say it's 17.x.x.x (not really the first octect). The 10 dot address is used solely on a fiber backbone and is used to perform system backups. It does not route to the 17 dot address range.
The problem is that the 17 dot address resolves fine from a remote workstation via DNS. So, if I ping the machine name 'app01mybusiness' from anywhere in the network, the name resolves the 17 dot address. However, if I go onto the local machine, and ping the same machine name "app01" it returns the 10 dot address.
The application installed on the server is a 3-party application (which means we cant modify it that much), and it registers the machine name in a remote database. Since it is entering the 10 dot address in the database, subsequent clients can't connect to the application server.
In the adapter, the 10 dot does not have a default gateway or DNS servers filled out. The 17 dot does have a gateway and a DNS server listed.
Bottom line: I need to get the local machine to resolve itself to the 17 dot address.
Since I'm a newbie, I don't have a lot of points to give so I'm throwing in all I got.