Networking Forums

Networking Forums > Computer Networking > Windows Networking > XP client cannot connect remote Domain

Reply
Thread Tools Display Modes

XP client cannot connect remote Domain

 
 
franklin
Guest
Posts: n/a

 
      11-27-2008, 06:02 PM
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 in my son's place:

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 new install
Between my son's place and my home we have a working 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.


 
Reply With Quote
 
 
 
 
Robert L. \(MS-MVP\)
Guest
Posts: n/a

 
      11-27-2008, 09:13 PM
Can you ping the SBS? by IP? If yes, can you ping it by name? If not, check
the DNS settings.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"franklin" <(E-Mail Removed)> wrote in message
news:42673$492eeeab$d594ee17$(E-Mail Removed) n.net...
>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 in my son's place:
>
> 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 new install
> Between my son's place and my home we have a working 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.
>
>


 
Reply With Quote
 
franklin
Guest
Posts: n/a

 
      11-28-2008, 02:16 PM
I can ping the server by IP and Name.

>Can you ping the SBS? by IP? If yes, can you ping it by name? If not, check
>the DNS settings.
>
>--
>Bob Lin, MS-MVP, MCSE & CNE
>Networking, Internet, Routing, VPN Troubleshooting on
>http://www.ChicagoTech.net
>How to Setup Windows, Network, VPN & Remote Access on
>http://www.HowToNetworking.com
>"franklin" <(E-Mail Removed)> wrote in message
>news:42673$492eeeab$d594ee17$(E-Mail Removed) on.net...
>>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 in my son's place:
>>
>> 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 new install
>> Between my son's place and my home we have a working 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.
>>
>>

>
>
>


 
Reply With Quote
 
Robert L. \(MS-MVP\)
Guest
Posts: n/a

 
      11-28-2008, 07:03 PM
any errors if running nslookup command?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"franklin" <(E-Mail Removed)> wrote in message
news:4e032$49300b5d$d594ee17$(E-Mail Removed) n.net...
>I can ping the server by IP and Name.
>
>>Can you ping the SBS? by IP? If yes, can you ping it by name? If not,
>>check
>>the DNS settings.
>>
>>--
>>Bob Lin, MS-MVP, MCSE & CNE
>>Networking, Internet, Routing, VPN Troubleshooting on
>>http://www.ChicagoTech.net
>>How to Setup Windows, Network, VPN & Remote Access on
>>http://www.HowToNetworking.com
>>"franklin" <(E-Mail Removed)> wrote in message
>>news:42673$492eeeab$d594ee17$(E-Mail Removed) ion.net...
>>>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 in my son's place:
>>>
>>> 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 new install
>>> Between my son's place and my home we have a working 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.
>>>
>>>

>>
>>
>>

>


 
Reply With Quote
 
franklin
Guest
Posts: n/a

 
      11-30-2008, 06:52 AM
No, that goes well.

nslookup domain.local gives me the right ip.

>any errors if running nslookup command?
>
>--
>Bob Lin, MS-MVP, MCSE & CNE
>Networking, Internet, Routing, VPN Troubleshooting on
>http://www.ChicagoTech.net
>How to Setup Windows, Network, VPN & Remote Access on
>http://www.HowToNetworking.com
>"franklin" <(E-Mail Removed)> wrote in message
>news:4e032$49300b5d$d594ee17$(E-Mail Removed) on.net...
>>I can ping the server by IP and Name.
>>
>>>Can you ping the SBS? by IP? If yes, can you ping it by name? If not,
>>>check
>>>the DNS settings.
>>>
>>>--
>>>Bob Lin, MS-MVP, MCSE & CNE
>>>Networking, Internet, Routing, VPN Troubleshooting on
>>>http://www.ChicagoTech.net
>>>How to Setup Windows, Network, VPN & Remote Access on
>>>http://www.HowToNetworking.com
>>>"franklin" <(E-Mail Removed)> wrote in message
>>>news:42673$492eeeab$d594ee17$(E-Mail Removed) tion.net...
>>>>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 in my son's place:
>>>>
>>>> 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 new install
>>>> Between my son's place and my home we have a working 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.
>>>>
>>>>
>>>
>>>
>>>

>>

>
>
>


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Remote Desktop: The client could not connect to the remote compute crazyglue Windows Networking 6 02-24-2009 08:26 AM
"The client could not connect to the remote computer. Remote connections..." - Server 2003 Maestro Windows Networking 4 10-25-2007 06:58 PM
"The client could not connect to the remote computer. Remote connections..." - Server 2003 Maestro Windows Networking 5 10-17-2007 01:14 AM
Xp pro client good only connect to one DC in the domain Nike23 Windows Networking 0 05-27-2007 09:29 PM
The Client could not connect to the remote computer hipnautic@gmail.com Windows Networking 1 08-30-2006 08:19 AM



1 2 3 4 5 6 7 8 9 10 11