Ok, I'll try to explain in the simplest terms possible, so someone can call me on missing the obvious solution.

We are starting to transistion over to a new network that our parent company has. All the IPs are in the form of 10.whatever. We drew the 10.99 network. The parent has a network of 10.1 (surprise there) and we currently have a 10.1 network as well. We are hosting our own dhcp/wins server and will be turning it off once the word comes down. We are however starting to turn some machines to the new network with static IPs.

Sorry for the MCSE-type question...
The proposed outcome is this:
  • Be able to access our servers by hostname from both networks.
  • Be able to ping machines on both networks by IP


The proposed solution was this:
  • Add another IP to the Server Nics for 10.99.whatever
  • Add both ours and their WINS servers in the configuration
  • Replace our internet DNS servers with their 10.1.whatever DNS servers


We've implemented this, and we can do the following:
  • Machine A (a desktop on new network) can ping Server A (w/ both network IPs).
  • Machine B (on old network) can attach to Server A via a desktop shortcut
  • Machine A (on new network) cannot attach to Server A via desktop shortcut
  • Server B (with dual IPs) can Ping/Attach to Server A (with Dual IPs) w/ primary IP of 10.1.whatever


We've added a static route (via ROUTE -P Add (Their WINS IP address) (Our 10.99 gateway)) for both Their WINS server and DNS servers (Since they are both 10.1 IPs). We can now ping their IPs, and they resolve to the correct hostnames.

What are we missing with the shortcuts? We're only missing 1 out of 4 criteria to get the machines cut over.

Any help would be appreciated.