DNS o Domain problem

  • Thread starter Thread starter ROB
  • Start date Start date
R

ROB

This is my problem:
I have two offices one in Miami the other one in Caracas.
Miami is the headquarter and in this office are running
the DNS server, Exchange server and the Domain controller.
Caracas is running as a memeber server with DHCP and WINS
servers on it. Our connection is through VPN but not VPN
Windows.
The point is, 2 weeks ago we got problem with the VPN
connection after fix the problem, In the server from
Caracas i got WINS problem with different IP address,
after a little information about this I fixed the problem,
but now is the big one, after have fixed the WINS problem
no body can login to the network... how the DNS is in
Miami well I thought we have problem with the VPN
connection probably that is the reason because they can't
login, but the problem is they can't login locally,
internally in the Caracas office, in other words they
can't login to the server right there, basically they have
two options to login....
first one, login as a local Administrator
Second one, re-starting their computers without connection
to the network, in other words disconnecting the cable
from the NIC card, once they got login to the netwrok and
got icons on the desktop then they connect the cable to
the NIC card and then they can run under the same domain,
same network and we can see the computer, send and receive
e-mails and also inter-exchange message with messenger.

I make a nslookup and everything is fine... I can ping
everything from miami and from caracas to miami, I don't
have any problem pinging names and/or Ip addresses after
they login under the second option, the
DNS IP address from the stations of Caracas are pointing
to the DNS server in Miami and the DNS ip address in the
server too.
Everytime when somebody try to login including domain
administrators they receive the following message on the
screen:
"WINDOWS CAN NOT CONNECT TO THE DOMAIN BECAUSE THE DOMAIN
CONTROLLER IS BLOCKED OR NOT AVAILABLE OR BECAUSE WINDOWS
DID NOT FOUND THE ACCOUNT OF YOUR PC. IF THE PROBLEM
PERSIST CONTACT YOUR ADMINISTRATOR"

At this point I'm not clue with this issue

Your help will be greatly appreciated.

I hope to be hearing from somebody soon.

Thank you very much
 
In
ROB said:
This is my problem:
I have two offices one in Miami the other one in Caracas.
Miami is the headquarter and in this office are running
the DNS server, Exchange server and the Domain controller.
Caracas is running as a memeber server with DHCP and WINS
servers on it. Our connection is through VPN but not VPN
Windows.
The point is, 2 weeks ago we got problem with the VPN
connection after fix the problem, In the server from
Caracas i got WINS problem with different IP address,
after a little information about this I fixed the problem,
but now is the big one, after have fixed the WINS problem
no body can login to the network... how the DNS is in
Miami well I thought we have problem with the VPN
connection probably that is the reason because they can't
login, but the problem is they can't login locally,
internally in the Caracas office, in other words they
can't login to the server right there, basically they have
two options to login....
first one, login as a local Administrator
Second one, re-starting their computers without connection
to the network, in other words disconnecting the cable
from the NIC card, once they got login to the netwrok and
got icons on the desktop then they connect the cable to
the NIC card and then they can run under the same domain,
same network and we can see the computer, send and receive
e-mails and also inter-exchange message with messenger.

I make a nslookup and everything is fine... I can ping
everything from miami and from caracas to miami, I don't
have any problem pinging names and/or Ip addresses after
they login under the second option, the
DNS IP address from the stations of Caracas are pointing
to the DNS server in Miami and the DNS ip address in the
server too.
Everytime when somebody try to login including domain
administrators they receive the following message on the
screen:
"WINDOWS CAN NOT CONNECT TO THE DOMAIN BECAUSE THE DOMAIN
CONTROLLER IS BLOCKED OR NOT AVAILABLE OR BECAUSE WINDOWS
DID NOT FOUND THE ACCOUNT OF YOUR PC. IF THE PROBLEM
PERSIST CONTACT YOUR ADMINISTRATOR"

At this point I'm not clue with this issue

Your help will be greatly appreciated.

I hope to be hearing from somebody soon.

Thank you very much
Click to expand...

Was there any changes made with the VPN from the default settings? If the
MTU settings were changed, say if they were dropped below 1500, probably to
optimize video conferencing traffic, or for some other reason, this will
cause *many* problems with AD, including logon, replication, and many
others.

MTU settings below 1500 will block LDAP, Kerberos and RPC traffic. They are
*required* for AD functionality.

Nslookup and ping are not affected by MTU size alterations.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top