[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 477
  • Last Modified:

Workstations cannot find/join a domain. Need help setting up a DC.

Okay, I'm very new at this so you'll have to be patient w/me.
First the Hardware setup:
I have a brand new server running W2K3.  The server has two NIC's. (One NIC is set up to obtain IP/DNS automatically, the other has a static IP address & DNS address defined.) The NIC's are both plugged into a small Linksys switch. There are also three workstations running XP Pro, both plugged into the Linksys switch. There is a cable modem running DHCP & DNS. The modem is also plugged into the switch.

The server is running AD & DNS. All machines have internet access, but none of the workstations can see the server.
When I run 'ipconfig /all' on the server it lists both the modem's NIC and the Servers NIC w/the static IP.
When I run it on a workstation, I only see the modem's NIC.  I can't ping the server by name or address.
If I run nslookup (server.domain.name) on the server, I get-
-----------------------------------------------------------------------------------------------------------------------------
***Can't find server name for address 192.168.0.10: Non-existant domain
Server: Unknown
Address: 192.168.0.10

Name: (server.domain.name)
Addresses: 192.168.0.10, 10.1.10.34
-----------------------------------------------------------------------------------------------------------------------------
When I run nslookup (server.domain.name) on a workstation I get-
-----------------------------------------------------------------------------------------------------------------------------
***Can't find server name for address 10.1.10.1:  Non-exixtent domain
***Default servers are not available
Server: Unknown
Address: 10.1.10.1

DNS request timed out.
      timeout was 2 seconds.
***Unknown can't find (server.domain.name): Non-existent domain
----------------------------------------------------------------------------------------------------------------------------
Is the problem caused by the fact that the modem is running DNS also?
I really don't know where to start... Please help.
0
RVicente99
Asked:
RVicente99
  • 27
  • 23
  • 2
1 Solution
 
youre1mCommented:
What DNS settings do you have configured on the workstations, sounds like you don;t have one specified. (Run ipconfig /all to check). If you don''t have one specified set a static DNS entry to your 2003 DC on a workstation and test again.

For a long term solution you can either issue the DNS settings with from your DHCP scope or set them statically on each client.
0
 
RVicente99Author Commented:
Sorry, I had already tried this and it didn't help...
I have specified a static DNS entry on a workstation.  When I run ipconfig /all it lists the IP address that I entered in the TCP/IP properties for a DNS server, but it still won't let me join the domain. (A domain controller for the domain 'server.domain.name' could not be contacted...)  I can't even ping the server from the workstation. (Either by name or IP address.)  Still in a bind...
0
 
youre1mCommented:
Have you installed sp2 on your XP machines? If so disable the firewall and try again. Also if you have any third party firewall software disable that too.

Also have you verified your ip address, does the subnet match that of the server? Is it in the same range as the server, can the server ping the xp workstations? etc.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
crissandCommented:
If you have a domain, it is better to use dhcp and dns from the domain, not from another machine (like the router). The configuration must look like this:

                        Internet
                    router
192.168.0.254  |   I understand the switch and router are the same apparatus, but this is a logical scheme
                   switch
192.168.0.1 |          | dhcp enabled in 192.168.0.xxx network
         server      workstation

The addresses from the scheme are just suggestions

Now, the server is domain controller, as you said, I mean you have already run dcpromo on it. When you dcpromo a server, it install the dns if there is another dns in the domain. I recommend installing dhcp on the server, and announce the workstation(s) thru dhcp the addresss, network mask, dns address (192.168.0.1) and default gateway (192.168.0.254). The dns's address and the router's address must be outside the dhcp pool, in the example start dhcp poll from 192.168.0.10 and end at 192.168.0.250.

If you want to use the second nic in the server, give it an adress like 192.168.0.2, and configure dhcp to announce this address too, like dns address. You'll have to create two A entries in the dns, one for every nic, with the same name, and activate round robbin.

I think it's enough by now.
0
 
RVicente99Author Commented:
I've turned off the firewalls, and changed the IP address for the NIC card on the server (it was outside of the DHCP pool.)
Now I can ping the workstations, and the workstations can ping the server, but they still cannot join the domain.
I still get - "A domain controller for the domain 'server.domain.name' could not be contacted..." and I still get this error when I run nslookup server.domain.name -
***Can't find server name for address 10.1.10.250: Non-existant domain
Server: Unknown
Address: 10.1.10.250

Name: server.domain.name
Addresses: 10.1.10.34, 10.1.10.250

I will try setting up DHCP again, but I'm not sure that's my problem.  Also, I want to remind you that the cable-modem is also running DHCP & DNS, and my ISP will not allow me to turn these off on the modem.  If the cable modem is running DHCP and handing out addresses in the 10.1.10.# pool, should I set DHCP on the server to use this same pool or should I set it up w/a different range?  Still not sure how this will allow the workstations to join the domain.
Thanks for your help so far....
0
 
crissandCommented:
Let's adjust the scheme with the new information provided by you:

                  Internet
                       | IP address provided by the ISP
                    router
    10.1.10.254  |  
                   switch
    10.1.10.1 |        | dhcp enabled in 10.1.10.xxx network
           server     workstation

The dhcp scope will then be 10.1.10.10-10.1.10.250/ netmask if there are less than 240 computers can be 255.255.255.0/ defaul gateway 10.1.10.254 (lan port of the router).

Do, or adapt these addresses and run ipconfig/all on the domain controller and on one workstation. Write the result of ipconfig here, to continue the diagnose and to try solving the problem.
0
 
RVicente99Author Commented:
Okay... I have DHCP running using the scope suggested above.
Here are the ipconfig/all results for the DC and one workstation...

Domain Controller:
C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : PowerEdge700
   Primary Dns Suffix  . . . . . . . : European-Auto.Local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : European-Auto.Local
                                       wp.comcast.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : wp.comcast.net
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
   Physical Address. . . . . . . . . : 00-0E-0C-60-0B-DE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 10.1.10.34
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.10.1
   DHCP Server . . . . . . . . . . . : 10.1.10.1
   DNS Servers . . . . . . . . . . . : 10.1.10.1
   Lease Obtained. . . . . . . . . . : Thursday, November 11, 2004 11:44:12 PM
   Lease Expires . . . . . . . . . . : Thursday, November 18, 2004 11:44:12 PM

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : European-Auto.local
   Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection
   Physical Address. . . . . . . . . : 00-C0-9F-4C-29-32
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.1.10.254
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.10.1
   DNS Servers . . . . . . . . . . . : 10.1.10.254

Workstation 1:
C:\Documents and Settings\Lou Viscusi>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : D40N1V51
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : european-auto.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : european-auto.local
        Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
        Physical Address. . . . . . . . . : 00-0F-1F-98-B3-31
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 10.1.10.96
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.1.10.1
        DHCP Server . . . . . . . . . . . : 10.1.10.1
        DNS Servers . . . . . . . . . . . : 10.1.10.254
        Lease Obtained. . . . . . . . . . : Friday, November 12, 2004 3:38:27 PM

        Lease Expires . . . . . . . . . . : Friday, November 19, 2004 3:38:27 PM

Just thought I'd add - Whenever I ping the server from the workstation (or vice versa) using the computer names I get a message "Ping request could not find host..."  However, if I ping using the IP addresses, it's fine.

Also, when I run nslookup European-Auto.local, I get:
*** Can't find server name for address 10.1.10.254: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  10.1.10.254

Name:    European-Auto.local
Addresses:  10.1.10.254, 10.1.10.34
0
 
RVicente99Author Commented:
Sorry... One more note...
I swapped the IP assignments suggested by crissand...
I used 10.1.10.254 for the server instead of the router because the router was already using 10.1.10.1
0
 
crissandCommented:
Ok. The dns suffix on workstation is european-auto.local, on the server is European-Auto.local, and you searched for European-Auto.local. Use a single name for all.

You can try pinging a station by IP with -a option, to see if dns record exists.


0
 
RVicente99Author Commented:
Ok. Here's an update. I didn't have Netbios over TCP/IP enabled.  I've done that.
Also, I noticed that I had no Reverse lookup zones. I've added one since.
Now nslookup seems to be returning all the proper values.  Also, I am able to ping the workstation & server
by ip address & dns name just fine, however, when I ping the domain name, I get a reply from the
routers ip address?, not the DC.  After all of this, I tried once again to join the domain with the xp workstation
and I still got "A domain controller for the domain 'server.domain.name' could not be contacted..." etc.
After some digging, I found that I was missing an SRV record.  When I went to DNS to add the SRV record, I noticed that within my forward lookup zones, my _msdcs folder was empty (With the exception of one NS record.)  None of the required folders (ldap, tcp, etc.) were in the _msdcs folder, and I'm not sure how to add them, or if I can.
I think this may be the cause of my headaches.  I tried removing DNS and reinstalling, but that didn't do it.
Do I need to remove/reinstall Active Directory and DNS?  Don't know what to do...
0
 
crissandCommented:
See here:

http://support.microsoft.com/kb/241505/EN-US/

In the forward lookup zone do you have an A for the server? Also, there must be a PTR entry in the reverse lookup zone for the same machine.
0
 
RVicente99Author Commented:
Okay.  Went to http://support.microsoft.com/kb/241505/EN-US/...
Everything was at it should've been. Also, verfied that I have an A & PTR for the server.
Then I ran netdiag /fix.  Everything but the DNS test passed fine, here are the DNS test results:

DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'PowerEdge700.European-Auto.Local.'. [RCODE_SERVER_FAILURE]
            The name 'PowerEdge700.European-Auto.Local.' may not be registered in DNS.
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.8e32a59a-0e05-4f44-8c81-bcd0a56e5bf6.domains._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry f219eeb9-586c-4374-a334-26adeedd2118._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '10.1.10.254'.
    [FATAL] No DNS servers have the DNS records for this DC registered.

Help...
0
 
crissandCommented:
There is something with the machine PowerEdge700 used as dns. There must be record for it in forward lookup zone: A and NS, and a PTR in reverse lookup zone. The dns server must be primary, active directory integrated.
0
 
RVicente99Author Commented:
In my forward lookup zone I had one NS record.  This record had 2 IP addresses listed for the FQDN (.254 & .34).
The PTR records seemed fine, there was one for the server and one for each workstation.
There are 5 A records -
      2 were labeled 'same as parent folder', one for each IP address (.254, .34)
      2 for the PowerEdge700, one for each IP address
      1 for an XP workstation on the same switch.

Just thought I'd mention again... This server has two NIC's.  One is set up w/a Static IP (.254) and the other is set up
to obtain IP/DNS automatically (right now it's .34).  Both are plugged into the same switch box that the cable modem is plugged into.  Could this second NIC be part of the problem?
0
 
crissandCommented:
Normally it can work, if there is another dhcp server. If the machine is dhcp server too, configure the second nic with a fixed address, like .253.

Is the dns primary?
0
 
RVicente99Author Commented:
The modem & the server are both running dhcp.
If I configure the second nic w/a fixed IP, I lose my internet connection.
As I mentioned in the very beginning, I'm new at all this, so... How do I know if the dns is primary?
0
 
crissandCommented:
In a network must be one dhcp for a scope. If you have two, within the same scope, it's a disaster.

Look at dns properties.
0
 
RVicente99Author Commented:
Okay... I've tried changing scopes..., configuring the second nic w/a static ip...,
removing dhcp on the server... none of it worked.

I'm seriously considering scrapping this install, and starting from scratch...
Anyway, below are the results of the latest netdia /fix:
DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'PowerEdge700.European-Auto.Local.'. [RCODE_SERVER_FAILURE]
            The name 'PowerEdge700.European-Auto.Local.' may not be registered in DNS.
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.8e32a59a-0e05-4f44-8c81-bcd0a56e5bf6.domains._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry f219eeb9-586c-4374-a334-26adeedd2118._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '10.1.10.68'.
    [FATAL] No DNS servers have the DNS records for this DC registered.

Anyone have any more suggestions?
0
 
crissandCommented:
The zone is European-Auto.local, the same as the domain, isn't it?
You have defined PowerEdge700 as primary dns for the zone?
You have a A record for PowerEdge700 in forward lookup zone and a PTR record in reverse lookup zone.
The dns is active directory integrated?
When you open DNS properties, what name or address do you find for the dns?
Are there other dns servers?
0
 
RVicente99Author Commented:
Yes, yes, yes, yes, poweredge700, and no.
0
 
crissandCommented:
Why are two names for the same machine, PowerEdge and poweredge? Or is just an error of writing?
0
 
RVicente99Author Commented:
DNS name is POWEREDGE700, address is 10.1.10.68
0
 
RVicente99Author Commented:
There were two IP addresses listed in the DNS properties... (10.1.10.68 & .34)
The second one is the address assigned by dhcp on the modem to the second nic.
I removed the second one and ran another netdiag /fix.  The results were a little better
but DNS still failed.

DNS test . . . . . . . . . . . . . : Failed
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.8e32a59a-0e05-4f44-8c81-bcd0a56e5bf6.domains._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry f219eeb9-586c-4374-a334-26adeedd2118._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '10.1.10.68'.
    [FATAL] No DNS servers have the DNS records for this DC registered.

0
 
crissandCommented:
let's see now the result of ipconfig /all on the server.
0
 
RVicente99Author Commented:
Below are results of ipconfig /all followed by results of nslookup *

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : PowerEdge700
   Primary Dns Suffix  . . . . . . . : European-Auto.Local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : European-Auto.Local
                                       wp.comcast.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : wp.comcast.net
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
   Physical Address. . . . . . . . . : 00-0E-0C-60-0B-DE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 10.1.10.34
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.10.1
   DHCP Server . . . . . . . . . . . : 10.1.10.1
   DNS Servers . . . . . . . . . . . : 10.1.10.68
                                       10.1.10.1
   Lease Obtained. . . . . . . . . . : Wednesday, November 17, 2004 11:34:31 PM
   Lease Expires . . . . . . . . . . : Wednesday, November 24, 2004 11:34:31 PM

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : european-auto.local
   Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection
   Physical Address. . . . . . . . . : 00-C0-9F-4C-29-32
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.1.10.68
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.10.1
   DNS Servers . . . . . . . . . . . : 10.1.10.68
                                       10.1.10.1

C:\Documents and Settings\Administrator>


C:\Documents and Settings\Administrator>nslookup
Default Server:  poweredge700.european-auto.local
Address:  10.1.10.68

> european-auto.local
Server:  poweredge700.european-auto.local
Address:  10.1.10.68

Name:    european-auto.local
Addresses:  10.1.10.68, 10.1.10.34

> poweredge700
Server:  poweredge700.european-auto.local
Address:  10.1.10.68

Name:    poweredge700.European-Auto.Local
Address:  10.1.10.68

> 10.1.10.68
Server:  poweredge700.european-auto.local
Address:  10.1.10.68

Name:    poweredge700.european-auto.local
Address:  10.1.10.68
0
 
crissandCommented:
I want to understand the topology. The standard looks like this:

                          Internet
                              |
                          ROUTER ? The cable modem is router too?
                               |
                          SWITCH
                         | |        |
                      SERVER   WORKSTATION

Am I right, or you want to use the server as router, because in that situation the topology must be changed.

The dns suffix and the connection specific dns suffix must be the same: european-auto.local, as the zone name. More, after your answer.
0
 
RVicente99Author Commented:
The topology is exactly as you described above, except that there is no router.
(Unless the cable modem is also a router, which I'm not aware of...)
So it's...
                Internet
                     |
             Cable Modem (running dhcp)
                     |
            Linksys Switch
            ||               |||
         Server        XP Workstations

DNS suffix, and connection specific DNS suffix (on both nics) are the same as the Zone Name....
0
 
crissandCommented:
I understand that you have a dhcp server on the cable modem/router. Do you need your computers or the server to be visible from the Internet? Anyway, I don't understand why the Connection-specific DNS Suffix  for the nic 1 is wp.comcast.net, because that domain doesn't exists, it's comcast.net that exists, but you don't exactly need to change information with AT&T WorldNet Services, I guess. Or you domain is part of at&t network?

If the cable modem doesn't have any firewall properties you are at great risk here: anybody from the Internet can access your server and workstations.
0
 
RVicente99Author Commented:
I have since changed the connection-specific DNS suffix for nic1 to european-auto.local
No my domain is not part of at&t network, where did that come from???
Yes, the cable modem also serves as a firewall.  I will be adding better firewall protection once this is all
up and running, but I just want to get this network up first...  below is a new ipconfig /all resut-

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : PowerEdge700
   Primary Dns Suffix  . . . . . . . : European-Auto.Local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : European-Auto.Local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : european-auto.local
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
   Physical Address. . . . . . . . . : 00-0E-0C-60-0B-DE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 10.1.10.34
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.10.1
   DHCP Server . . . . . . . . . . . : 10.1.10.1
   DNS Servers . . . . . . . . . . . : 10.1.10.68
                                       10.1.10.1
   Lease Obtained. . . . . . . . . . : Thursday, November 18, 2004 11:45:51 AM
   Lease Expires . . . . . . . . . . : Thursday, November 25, 2004 11:45:51 AM

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : european-auto.local
   Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection
   Physical Address. . . . . . . . . : 00-C0-9F-4C-29-32
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.1.10.68
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.10.1
   DNS Servers . . . . . . . . . . . : 10.1.10.68
                                       10.1.10.1
0
 
crissandCommented:
Now, let's see. The topology with addresses:

                Internet
                     | Addresss from the ISP
             Cable Modem (running dhcp)
                     | 10.1.10.1
            Linksys Switch
10.1.10.68||10.1.10.34
           Server

Go to every nic property and remove 10.1.10.1 as dns server. To use the router as dns, use the forwarders option of the dns server. Choose all domains (or something like this) and add 10.1.10.1 as the address where the forward will go. Then run netdiag again, to see if there are errors.
0
 
RVicente99Author Commented:
Ok... 10.1.10.1 has been removed as dns server from all nics, and added to the forwarders list in dns.
Netdiag results follow:

    Computer Name: POWEREDGE700
    DNS Host Name: PowerEdge700.European-Auto.Local
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
    List of installed hotfixes :
        Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

    Adapter : Local Area Connection 2

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : PowerEdge700
        IP Address . . . . . . . . : 10.1.10.254
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.1.10.1
        Dns Servers. . . . . . . . : 10.1.10.254


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
            No remote names have been found.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : PowerEdge700.wp.comcast.net
        IP Address . . . . . . . . : 10.1.10.34
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.1.10.1
        Dns Servers. . . . . . . . : 10.1.10.1


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
            No remote names have been found.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{252FD380-8004-4692-B444-B865CBEE2669}
        NetBT_Tcpip_{72E611D8-D82E-4054-82AD-513DB4EA5A9D}
    2 NetBt transports currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'PowerEdge700.European-Auto.Local.'. [RCODE_SERVER_FAILURE]
            The name 'PowerEdge700.European-Auto.Local.' may not be registered in DNS.
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.8e32a59a-0e05-4f44-8c81-bcd0a56e5bf6.domains._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry f219eeb9-586c-4374-a334-26adeedd2118._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.254' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '10.1.10.254'.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{252FD380-8004-4692-B444-B865CBEE2669}
        NetBT_Tcpip_{72E611D8-D82E-4054-82AD-513DB4EA5A9D}
    The redir is bound to 2 NetBt transports.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{252FD380-8004-4692-B444-B865CBEE2669}
        NetBT_Tcpip_{72E611D8-D82E-4054-82AD-513DB4EA5A9D}
    The browser is bound to 2 NetBt transports.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
0
 
RVicente99Author Commented:
Sorry...I posted the wrong log... This is the current one.




    Computer Name: POWEREDGE700
    DNS Host Name: PowerEdge700.European-Auto.Local
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
    List of installed hotfixes :
        Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

    Adapter : Local Area Connection 2

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : PowerEdge700.european-auto.local
        IP Address . . . . . . . . : 10.1.10.68
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.1.10.1
        Dns Servers. . . . . . . . : 10.1.10.68


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
            No remote names have been found.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : PowerEdge700.european-auto.local
        IP Address . . . . . . . . : 10.1.10.34
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.1.10.1
        Dns Servers. . . . . . . . : 10.1.10.68


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
            No remote names have been found.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{252FD380-8004-4692-B444-B865CBEE2669}
        NetBT_Tcpip_{72E611D8-D82E-4054-82AD-513DB4EA5A9D}
    2 NetBt transports currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.8e32a59a-0e05-4f44-8c81-bcd0a56e5bf6.domains._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry f219eeb9-586c-4374-a334-26adeedd2118._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.European-Auto.Local. re-registeration on DNS server '10.1.10.68' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '10.1.10.68'.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{252FD380-8004-4692-B444-B865CBEE2669}
        NetBT_Tcpip_{72E611D8-D82E-4054-82AD-513DB4EA5A9D}
    The redir is bound to 2 NetBt transports.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{72E611D8-D82E-4054-82AD-513DB4EA5A9D}
        NetBT_Tcpip_{252FD380-8004-4692-B444-B865CBEE2669}
    The browser is bound to 2 NetBt transports.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
0
 
crissandCommented:
You have changed again the dns server address. Go to dns properties and reconfigure all options to point to that address 10.1.10.254. As you can see, the dhcp server is giving the second card an address and a host name. Is this normal, imposed by the ISP, or just a bad configured router/dhcp?

I'll go to the next configuration: disable the dhcp from the cable modem. Install dhcp on the domain controller. Give the two nics of the domain controller fixed addresses 10.1.10.1 and 10.1.10.2. Give the lan port of the cable modem/router address 10.1.10.254. Configure dhcp with a scope of 10.1.10.11 to 10.1.10.250. Configure dhcp to give workstation the netwmask of 255.255.255.0, the default gateway of 10.1.10.254. Configure dns to forward requests to 10.1.10.254, and to listen to the two local nics 10.1.10.1 and 10.1.10.2 with round robbin active.

And that's all, the network must work and the Internet will be available for all workstations and server. Don't enable any software firewall, on server or workstations if the cable modem has firewall.
0
 
RVicente99Author Commented:
I think you missed my last posting where I stated that I incorrectly posted an old netdiag,
then posted the most recent one.  We must have crossed each other...
Anyway, I didn't change the dns server address again, and DHCP is not giving the nic an address and a host name...
Please see my previous posting for the correct netdiag results...
0
 
crissandCommented:
Would you consider what configuration I suggested. No DNS and no dhcp on the router, dhcp and dns on the domain controller. I recommend uninstalling dns, changing the ip addresses, and reinstalling dns.
0
 
RVicente99Author Commented:
ISP will not turn dhcp off on the modem...
0
 
crissandCommented:
It's their modem? I don't understand why? The lan part of the network is in your administration, if they use dhcp for the wan part is their business. It's the first time I heard an ISP asking for dhcp in a local network.
0
 
RVicente99Author Commented:
Okay... I've pretty much started from scratch.  I've decided to create a workgroup instead, but I'm still having some
problems.  Once again, the workstations are all XP pro machines and the server is W2K3 server.
The server is set up as a file and print server, and all of the machines are part of the same workgroup.

Here's the topology:
                                                  Internet
                                                      |
                                        Cable Modem/Router (running dns/dhcp)
                                                      |
                                             Linksys Switch
                                                |            |||
                                            Server       XP Pro machines

All nic's have a static ip address (outside of the dhcp scope) and point to the modem/router as their gateway & their preferred dns server. All machines can access the internet just fine. Here's the problem, although the server can ping all of the workstations they don't show up in the workgroup.  All of the xp workstations can ping each other fine, and they can share documents and printers with no problem, but none of them can ping the server.  When I view the workgroup computers from the workstations, the server shows up, but I can't access anything from it.

What am I missing?  Or is my configuration all wrong?  I know that you can set up W2K3 in a workgroup, and that MS recommends it for networks w/less than 10 computers, but aside from entering the workgroup name into the 'machine name' section of the control panel/performance maint/system/... I don't know what else to do.  I have created a shared partition on the server.
0
 
crissandCommented:
You have to disable Internet Connection Firewall on the server and machines, or open the necessary ports (135, 136, 139). If you use netbios, see that enable netbios over tcp/ip is selected on all machines TCP/IP configuration.
0
 
RVicente99Author Commented:
Firewalls were already disabled, and netbios over tcp/ip was already enabled...
How would I open ports 135,136,139?
0
 
crissandCommented:
You don't need to open ports if firewall is disabled (there are no closed ports). I hope netbios over tcp/ip is enabled on the server too and the ICF is disabled there too.

Now your network looks like the one at my home (just 2 workstations), but I don't use the router's dhcp service, but I have dhcp and DNS on the w2k3 server.

Verify if the server's nic has address in the same network as the workstations. Verify using ipconfig /all if the netmask, default specific dns sufix and default gateway are the same on workstations and server.
0
 
RVicente99Author Commented:
Netbios over tcp/ip is enabled on the server... what is the ICF?
The server and workstations all have ip addresses in the 10.1.10.### range, and they are all on the same subnet.  
What I'm not sure about is whether this is the same subnet that the router is using... but I don't think
that would matter would it?
0
 
crissandCommented:
Internet connection firewall.

As for you question, it's surely the same network as the lan port of the router, otherwise no Internet connection.

Are the following services running on the server: tcp/ip netbios helper and computer browser? Now all you have to do is:
1.Shut down all workstations.
2.Restart the server.
3.Start the workstations.

Verify if the computers are visible in the network.
To access the share on the server, you have two ways: enable guest account (very insecure), or create acoounts for each user from each workstation. If there are users with blank passwords, give them a password non blank.
0
 
RVicente99Author Commented:
Okay I've checked or done all of the above.  When I go to verify if the computers are visible in the network..
(by this I assume they show up in the workgroup)  The answer is yes for the workstations, and no for the server...
Just like before, nothing has changed...
I can see all of the machines in the workgroup from the workstations, however I still cannot access the server...
("Servername is not accessible.  You might not have permission to use the network resource. Contact the admin. of this
server to find out if you have access permission.  The network path was not found.")

From the server, I cannot see any of the machines in the workgroup...
("No permission to view this network...")

Also, I still cannot ping the server from the workstations, but the workstations can ping each other and the server
can ping everthing...  
0
 
crissandCommented:
Ok, let's see ipconfig /all on the server and on one workstation. Please, verify if the workstation and server services are started.
0
 
RVicente99Author Commented:
Services (tcp/ip netbios helper and computer browser) are running on the server & workstations.

ipconfig /all for server:
C:\Documents and Settings\Administrator.POWEREDGE700>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : PowerEdge700
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
   Physical Address. . . . . . . . . : 00-0E-0C-60-0B-DE
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.1.10.205
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.10.1
   DNS Servers . . . . . . . . . . . : 10.1.10.1

ipconfig /all for workstation:
C:\Documents and Settings\Lou Viscusi>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Cont
roller
        Physical Address. . . . . . . . . : 00-0F-1F-98-B3-31
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 10.1.10.200
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.1.10.1
        DNS Servers . . . . . . . . . . . : 10.1.10.1
0
 
crissandCommented:
Ok. Verify again if Internet connection firewall not to be active on the server's nic. Do you really need ip routing enabled?

Can you ping the server using its IP?
0
 
RVicente99Author Commented:
No firewalls are active anywhere in the network.  No, I cannot ping the server using it's IP.  The server can ping the
workstations, and the workstations can ping each other, but none of them can ping the server.

Not sure about IP routing being enabled on the server, if I don't need it, I guess I can disable it...
How do I do that? Is it a service?
0
 
crissandCommented:
When you enter nic's properties is a tab called Authentication. See if all options are disabled, or greyed. Then in the advanced tab, there is the firewall that you said is disabled.

For ip routing you must disable the bridge between the two network boards; I see now that you are using only one.

If you have routing and remote access service running, stop it.
0
 
RVicente99Author Commented:
On the Authentication tab, two of the three options are checked
The first one: Enable IEEE 802 1x authentication for this network
           EAP type 'Smart card or other certificate'
The second one: Authenticate as computer when computer information is available.

Yes, I am sure that the firewall is disabled.

Routing & Remote Access service has been stopped.
I will try all connections again and post results shortly.
0
 
RVicente99Author Commented:
That was it!   I turned off Routing & Remote Access on the server and all is now well.
Everyone can see the server, server can see everyone, everyone has internet access.
Thanx for all your help (and patience)... The points are yours.
0
 
crissandCommented:
Happy to help!
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 27
  • 23
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now