Possible. It could also be that an app is trying to open a listening socket on a particular port and something else has already done that so the port is locked. I'd have a check what's in the user's login prefs in terms of applications that start at login.
Although the fact it works in different locations does suggest something to do with DHCP, since that's subnet specific. In which case it isn't that computer that's got a fault, it's another one. Caz, can people configure their own network settings or is it locked off to admin only?
Jon