|
|
Hallo allemaal,
A few days ago we moved our SBS 2003 server to another location
This server is AD, DHCP, Exhange, OWA and OMA serevr.
Before this server was in our home network, but now moved to my son's ouse.
Network un my son's house:
ADSL 2+
Modem
WatchGuard FireBox X20E
Client Vista Ultimate
Client XP Pro
In my place:
ADSL 2+
Modem
Linksys DSL VPN Router, DHCP and Gateway for my home network.
Client Vista Business
Client XP Pro verse installatie
Between my son's place and my home we have a VPN-tunnel.
My son's place:
SBS 2003 Server: IP 192.168.0.4
My place:
Linsys Router: IP 192.168.1.1
Client Vista Business:
IP 192.168.1.100 via DHCP
DNS server 192.168.0.4
Gateway 192.168.1.1
The XP client cannot connect to the AD. It can connect however with dial-in connection.
The Vista client log in is within a few seconds.
The XP client takes over 30 minutes to log in and than has no profile.
IP via DHCP and DNS server are allright according ipconfig /all
I don't have a clue what is going wrong here.
User and machine are both visible in AD.
Why can't the XP client connect to the domain.
|
|
In news:aeafb$492eecf0$d594ee17$26511[ at ]news.prolocation.net,
franklin <fbockstael[ at ]gmail.com> requesting assistance, typed the following:
[Quoted Text] > Hallo allemaal,
>
> A few days ago we moved our SBS 2003 server to another location
> This server is AD, DHCP, Exhange, OWA and OMA serevr.
> Before this server was in our home network, but now moved to my son's
> ouse.
>
> Network un my son's house:
>
> ADSL 2+
> Modem
> WatchGuard FireBox X20E
> Client Vista Ultimate
> Client XP Pro
>
> In my place:
>
> ADSL 2+
> Modem
> Linksys DSL VPN Router, DHCP and Gateway for my home network.
> Client Vista Business
> Client XP Pro verse installatie
>
> Between my son's place and my home we have a VPN-tunnel.
>
> My son's place:
> SBS 2003 Server: IP 192.168.0.4
>
> My place:
> Linsys Router: IP 192.168.1.1
>
> Client Vista Business:
> IP 192.168.1.100 via DHCP
> DNS server 192.168.0.4
> Gateway 192.168.1.1
>
> The XP client cannot connect to the AD. It can connect however with
> dial-in connection. The Vista client log in is within a few seconds.
>
> The XP client takes over 30 minutes to log in and than has no profile.
> IP via DHCP and DNS server are allright according ipconfig /all
>
> I don't have a clue what is going wrong here.
> User and machine are both visible in AD.
>
> Why can't the XP client connect to the domain.
Assuming the VPN tunnel is in place, and the routes and trusted networks are
setup correctly in the VPN properties on both sides, as well as that all
ports are allowed free access (no restrictions, it should work. What maybe
the issue is the ADSL. Since it is a slow link, it will fall under the
default AD threshold of 500Kb, which cause certain things portions of a GPOs
to not function. Also with an ADSL line, it uses PPPOE, which is known to
cause problems due to the lower MTU (1492 instead of 1500), which thwarts
domain communication.
My suggestion is check the firewall settings. Test to see if you can ping
the server from your place to your son's SBS. If that works, determine what
the MTU is by following this website's suggestions:
http://wansend.wordpress.com/2007/05/17/using-ping-to-find-largest-mtu-along-a-vpn-route/
If it is lower than 1492, there will be a problem, because Ldap has problems
under 1500.
ALso, if you get that working, and if you want to browse by network
neighborhood, you will also need WINS on the SBS and configure your clients
to use it.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
|
|
|