VLANS

Hello fellas:

I have a very rare situation here, some time ago I got a Novell Networking,
but now joining to Windows Server 2003, I have several locations in the
country conected between them via VLANS, when I try to connect my XP
workstations, to my domain I can see it, it responds to the ping, and it ask
me the administrator credentials, but Windows every time sends me the same
error, "Error to try to joint to the domain MYDOMAIN.COM, no network access
can be found".


Any ideas?, I have a feeling about the UDP/TCP ports between the vlans....

Most likely your workstation is not using the correct DNS Server. It needs
to use the DNS in the DC of the Domain it wants to join.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"Baruch Ortiz" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hello fellas:
>
> I have a very rare situation here, some time ago I got a Novell
Networking,
> but now joining to Windows Server 2003, I have several locations in the
> country conected between them via VLANS, when I try to connect my XP
> workstations, to my domain I can see it, it responds to the ping, and it
ask
> me the administrator credentials, but Windows every time sends me the same
> error, "Error to try to joint to the domain MYDOMAIN.COM, no network
access
> can be found".
>
>
> Any ideas?, I have a feeling about the UDP/TCP ports between the vlans....
>
>

Yes, infact the DNS is the same server, than the DOMAIN CONTROLLER....

and still showing the same....

"Phillip Windell" <@.> escribió en el mensaje
news:(E-Mail Removed)...
> Most likely your workstation is not using the correct DNS Server. It
> needs
> to use the DNS in the DC of the Domain it wants to join.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
> "Baruch Ortiz" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hello fellas:
>>
>> I have a very rare situation here, some time ago I got a Novell
> Networking,
>> but now joining to Windows Server 2003, I have several locations in the
>> country conected between them via VLANS, when I try to connect my XP
>> workstations, to my domain I can see it, it responds to the ping, and it
> ask
>> me the administrator credentials, but Windows every time sends me the
>> same
>> error, "Error to try to joint to the domain MYDOMAIN.COM, no network
> access
>> can be found".
>>
>>
>> Any ideas?, I have a feeling about the UDP/TCP ports between the
>> vlans....
>>
>>
>
>

I don't know then. VPN is a slow-link technology, perhaps it is running
too slow and the attempt is timing out. Keep in mind that on asyncronous
links (like ADSL) the upload speed is much slower than the "advertized
speed" and the VPN will always sync at and run at the slower "upload speed"
in both directions.

Anything else I could say would only be pointless "blind guessing".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------



"Baruch Ortiz" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Yes, infact the DNS is the same server, than the DOMAIN CONTROLLER....
>
> and still showing the same....
>
> "Phillip Windell" <@.> escribió en el mensaje
> news:(E-Mail Removed)...
> > Most likely your workstation is not using the correct DNS Server. It
> > needs
> > to use the DNS in the DC of the Domain it wants to join.
> >
> > --
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> > -----------------------------------------------------
> > Understanding the ISA 2004 Access Rule Processing
> > http://www.isaserver.org/articles/IS...cessRules.html
> >
> > Microsoft Internet Security & Acceleration Server: Guidance
> > http://www.microsoft.com/isaserver/t...dance/2004.asp
> > http://www.microsoft.com/isaserver/t...dance/2000.asp
> >
> > Microsoft Internet Security & Acceleration Server: Partners
> > http://www.microsoft.com/isaserver/partners/default.asp
> > -----------------------------------------------------
> >
> >
> > "Baruch Ortiz" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> Hello fellas:
> >>
> >> I have a very rare situation here, some time ago I got a Novell
> > Networking,
> >> but now joining to Windows Server 2003, I have several locations in the
> >> country conected between them via VLANS, when I try to connect my XP
> >> workstations, to my domain I can see it, it responds to the ping, and
it
> > ask
> >> me the administrator credentials, but Windows every time sends me the
> >> same
> >> error, "Error to try to joint to the domain MYDOMAIN.COM, no network
> > access
> >> can be found".
> >>
> >>
> >> Any ideas?, I have a feeling about the UDP/TCP ports between the
> >> vlans....
> >>
> >>
> >
> >
>
>

Try dropping the .com from the domain. I have seen this happen before..
Removing the suffix makes it work. I thought it was DNS to but
everything checked ok in that department. It took nothing more than
removing the .com from the domain when trying to add the machine.

psg