Problem in joining Domain

[nimamrsdy]

Hi ,
I installed windows 2003 Enterprise R2 on my server . It is Domain
Controller and DNS installed on it . everything seems OK . But I have Problem
when trying to join it's Domain.

In My Client Windows Vista I receive this message when I try to connect My
Domain:
"The format of the specified network name is invalid"

More Details :
My Client DNS server is the same as My server.
1 month ago I join my clients in a different domain name . I change it to
workgroup . after then I can't join any domain .

Please help me in this issue.
Thank you .

 

[Kerry Brown]

Please post the results of "ipconfig /all" for the domain controller and a
workstation that can't join the domain?

 

[nimamrsdy]

Thanks for your respons Kerry
Here is Ipconfig Results :
(Because of security , I use x , y . Sorry about this.Note : There is one
router between my Client And server. In other word The client and server IP
Range is different.)

Server Side (Windows Server Enterprise R2):

Windows IP Configuration
Host Name . . . . . . . . . . . . : sharepoint
Primary Dns Suffix . . . . . . . : synergy.net
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : synergy.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit
Ethernet Controller
Physical Address. . . . . . . . . : 00-1A-92-E7-A6-BF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 217.218.x.y
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . : 217.218.x.y
DNS Servers . . . . . . . . . . . : 217.218.x.y

Client Side (Windows Vista Ultimate)
Windows IP Configuration

Host Name . . . . . . . . . . . . : Nima-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Connection
Physical Address. . . . . . . . . : 00-1B-77-12-A7-74
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a167:b1f3:d9cf:578a%9(Preferred)
IPv4 Address. . . . . . . . . . . : 217.218.x.y(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 217.218.x.y
DNS Servers . . . . . . . . . . . : 217.218.x.y (Server IP Address)
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller
Physical Address. . . . . . . . . : 00-19-B9-6B-B6-48
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{C2E8CE06-4EE3-4F91-A655-65D602590878}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::200:5efe:217.218.180.182%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 217.218.x.y (Server IP Address)
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{D521D0F7-90C2-4C93-BFB5-8DAC24329C9D}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{AF703893-C77C-4A17-BEE6-B404F376615D}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Temporary IPv6 Address. . . . . . : 2002:d9da:b4b6::d9da:b4b6(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 217.218.x.y (server IP address)
NetBIOS over Tcpip. . . . . . . . : Disabled

 

[Kerry Brown]

Are you trying to set up a network using public IP addresses? This is a
really bad idea.

Without seeing the full IP address I can only guess that they are on
different networks as they have different subnet masks. If this is the case
then it's a routing problem. I don't want to pursue this as it sounds like
you are trying to network two sites over the Internet in a very insecure
fashion.

If they are at the same site then you would be much better off connecting a
router to the Internet and using a private network range for your internal
network. If they are not at the same site then you should be using a site to
site VPN to connect the sites with a domain controller at each site. For one
computer at a remote site you could use a VPN from the computer direct to
the LAN. You would need a router at both ends that does VPN passthrough and
then forward port 1723 to the VPN server on the server end. Whatever you do
it's not recommended to setup networking with public IP addresses. Your
network will be extremely vulnerable and you will have no end of routing
problems.

As an aside there is no privacy on the Internet. Obfuscating the results of
ipconfig /all doesn't help. Your IP address (217.218.xxx.135) is in the
header of your posts. Given the net mask it would be very simple to figure
out which IP address your server is using. Now do you see why using public
addresses for your LAN is a bad idea? You need to stop doing this and set up
a private network for your internal LAN.

By the name of the server "sharepoint" it looks like you are using
Sharepoint. If all you want to do is connect to Sharepoint there is no need
for a remote client to join the domain. You could use SSL to connect. The
Sharepoint server doesn't need to be exposed to the Internet. A
router/firewall with port 443 forwarded to the Sharepoint server would be a
much better setup. If you are already using port 443 for something else
Sharepoint can be configured to use a different port.

Maybe if you explain what you are trying to accomplish someone can offer a
more secure way to do it. As it stands it sounds like you have a very
insecure set up that will cause no end of problems when trying to use Active
Directory.

 

[nimamrsdy]

Thank you for your complete Response Kerry . I'm designing new topology fot
this situation . I have special thanks for your help my friend .

wish you best of best

 

[Kerry Brown]

You're welcome. Let us know how it works out.