|
Erik,
We went through a prototype phase for these "home worker" machines. With two variants:
1) One wkstn used a router to connect to DSL modem
2) One wkstn used a direct connect to DSL modem and PPP software driver.
They "the customer" along with some of "our" people (not me) made the descision to not use the router ... why ? I have not idea why. It also meant that we had to install a software firewall to protect the machine.
The root of the problem is that until the machine is connected to VPN, and because its still set to DHCP (which is how these machine are set in the office) ... the wkstn acts REALLY, REALLY sluggish during bootup, and during the initial login. In fact, because the bootup is so slow, things actually break (ie, startup tasks and services not starting properly) not all the time, but alot of times.
Once the machine is logged into VPN (after the second user logon for proper domain login &scripts) - the wkstn seems to pick-up steam.
The long part of this story is that we have tons of custom software on the wkstn (written by us) that is VERY network sensitive, therefore the hesitation to change anything. But, because we dont have a router serving-up IPs to the wkstn, I think I HAVE to convince the "customer" and "our guys" that going static IP is the only way to fix this.
In fact, I going to setup one of these wkstns on Monday and I am going to "slip-in" the static ip assignment and not tell anyone - if it breaks something, can always change back. If it works, we're laughing !
-Shawn
[ 07. June 2003, 19:52: Message edited by: Shawn ]
| 
