G
Guest
Here's a good one for us to ponder.....we have a client, that has a laptop on
a Small Business Server domain, that in the past, was hooked up to his home
network as the home network was named abc.local
So the home network was named a workgroup with abc.local and then laptop was
a domain pc with abc.local
Everything was peachy, until we installed and decided to rename the domain
to match the external domain. So now it's abcdefghijkl.local But when you
type the new domain into the workgroup field on his home network, I can't get
it to recognize the entire name, it stops at .lo can't get it to spell out
cal. I am thinking there is a naming length within Windows XP...so is there
a work around? I'm thinking there might be, but I don't want to create a vpn
to the network, and join his home pc's to the network, but I could, then just
drop the vpn, and he can still use the pc's off the network...
Let me know what you all think.....
Steven Babcock
(e-mail address removed)
a Small Business Server domain, that in the past, was hooked up to his home
network as the home network was named abc.local
So the home network was named a workgroup with abc.local and then laptop was
a domain pc with abc.local
Everything was peachy, until we installed and decided to rename the domain
to match the external domain. So now it's abcdefghijkl.local But when you
type the new domain into the workgroup field on his home network, I can't get
it to recognize the entire name, it stops at .lo can't get it to spell out
cal. I am thinking there is a naming length within Windows XP...so is there
a work around? I'm thinking there might be, but I don't want to create a vpn
to the network, and join his home pc's to the network, but I could, then just
drop the vpn, and he can still use the pc's off the network...
Let me know what you all think.....
Steven Babcock
(e-mail address removed)