Hi ian, and thanks... this is info that i put in the other thread plus extra info:
basically if you run a continuouse ping (IP ADDRESS) to the vectorworks installed p.c it replies fine, as soon as you fire up the vectorworks app the pings to it time out, and it loses its mapping to the 'share drive' it is unable to ping other p.c's on the same network but can ping its internet default gateway (on a home router)! (so not totally isolated) when you close the app the p.c remains in this state for about 40 minutes, even if you reboot the p.c!
The P.C's are hub'd there are 5 of them on the network, i thought about the flooding issue too, but the other p.c's can ping each other fine during this, and also the p.c's in question can ping the default gateway???
I am certain it is the app causing this, because it is clear just by doing the ping to the p.c its fine, until the moment the process for the app starts, and then it craps out
this is the same for both of the p.c's with the app installed.. have tried moving the mapped drive off of a vector works installed p.c to a.n other p.c but it is the same issue, as soon as the app is fired up it is affectivley isolated from other p.c's
Other information, just so you are completley in the picture, there are no other funky apps on the machines, just office products i.e etc. the software is a Japanese version as the company are based in Tokyo and it is fully licensed.
I'll get the ipconfig info from the users today.. thanks!