I am having somewhat of a struggle here with the job i'm working at know. I will try and make as good of a description of the problem as possible.
We have multiple laptop users who would like to work at home (off course). The issues we are seeing when they try to work at home is this. When thay have a network connection at home (cabled or wireless) login takes a long time (for about 3 to 4 minutes), it pauzes after the applying your personal settings screen and it just keeps sitting there with the nice blue XP background. When users login without any connection to the any kind of network, so really stand alone, everything works fine..
To point out some config settings we have. Our network has a complete external DNS structure, so no NATting done here. If i'm sitting at home it would be possible to ping my own machine. This means it is also possible to ping all of our DC's externally. I am not the administrator of the firewall, nor the network, but i do need to fix the slow logins for the users.
The things i've figured out this far (and also, please correct me if i'm wrong) is that domain members get a primary DNS suffix that is the same as the name of the domain. When i'm trying ot work at home i still have my Primary DNS suffix pointing to my domain meaning i'm able to ping domain machines only using the NETBIOS name. Second, it looks like the time out I'm receving when logging in is the TCP/IP timeout which (according to al the papers) is like 4 minutes.
I am aware that this isn't really something that is fixable within a minute or so, i would like to get some of your points of view regarding this issue. Maybe you can point me into the right direction? And please try not to point out the obvious, I am well aware that using a pingable DC isn;t best practice :) :)
Any help is appreciated