Share Problems between client & old server - new server /me pulls hairout

Hi gang,

I've got a mystery on my hands that I'm currently unable to solve. I
thought I'd toss in the info I have here to see if someone might be able to
help me out or just shed a bit more light into what's going on.

Background:

-I have server OLDSERVER running Win2003 Srv Std (no sp) and a share setup
on it called 'PANEL'
-Workstations A,B,C have a network drive (X mapped to \\oldserver\panel
where their app saves / loads its jobs from
- We decide to phase out OLDSERVER with NEWSERVER (2003srv std no sp)
- Setup a share on NEWSERVER called PANEL and copy all the data/jobs etc.
from \\oldserver\panel
- We remap workstations A,B and C to \\newserver\panel as X:
- I stop sharing \\oldserver\panel and actually rename the panel folder on
the servers local disk to 'OldPanelData'
- We load jobs from the workstations and all runs fine, OLDSERVER is
shutdown
- Workstation C tries to load a job with the app on X: and it takes about 30
seconds (not responding - eventually opens up fine)
- Clients A and B open up the jobs immediately
- When I turn on OLDSERVER again - Workstation C immediately opens up the
job. Turn it off, 30 seconds delay again
- I check the program App settings on Workstation C, no instance of
OLDSERVER, run through registry and remove any instance of OLDSERVER. The
files the program saves do not contain path information or UNC names.

So I install network monitor on OLDSERVER and have client C open up a job
and get this:
Protocol / Description / Source / Dest
SMB / C tree connect & X, Share = \\OLDSERVER\PANEL / StationC /
Oldserver
SMB / C tree connect & X - NT Error, System, Error, Code = 204
Status_Bad_Network_Name / Oldserver / StationC
SMB / C logoff & X / StationC / Oldserver
SMB / R logoff & X / Oldserver / StationC
SMB / C transact 2 NT Get DFS Referral / StationC / Oldserver
SMB / R transact 2 - NT Error, System, Error Code 14 Status_No_Such_Device /
Oldserver / StationC

My question is this: What is causing this Workstation C to continue to look
to the old server first? Eventually it times out and loads the job from the
new one. The workstation has been restarted, registry purged of 'oldserver'
references, no remaining network drives mapped to \\oldserver

I'd like to take this box down but this guy opens up a ton of files a day
and this will drive him batty if he is waiting for 30 seconds each time he
tries - esp. when the other 2 workstations using the same app and settings
work fine. For now I have the oldserver up and running basically just for
him as his workstation contacts it for whatever reason.

Any advice or insight *greatly* appreciated.


tsc