asked on

Can't join windows xp pro workstation to windows nt domain, can ping other workstations but not server

We run a small Windows nt 4 network, will a Dell server, 2 xp pro w/stations, 1 xp home w/station, 5 windows 98/ME w/stations. One of the xp pro computers stopped seeing the network. Don't know what could have changed, although computer set to automatically update Windows. After trying other things, reinstalled OS with OEM (Dell) CD-roms. That didn't help. Have read/tried everything I can get my hands on in this site and elsewhere. On the problem computer I can get to internet (via a router and T-1 bundle) and can ping other workstations on network, by name and IP, but I can't ping the server running our domain. I'm no IT expert, but as I understand it, the router is handling DHCP for our network, router is 10.0.0.1, server is 10.0.0.2 (fixed), the problem computer is being assigned 10.0.0.3, and the remaining computers have assigned IPs up through 10.0.0.10. I can ping to and from the problem computer from any workstation by name or IP. From the server I can ping workstations other the problem computer by IP but not by name. The problem computer can't ping the server by name or IP and the server can't ping the problem computer by name or IP. When I run ipconfig /all on the workstations, they all report the same info, so they all seem to be configured the same way.

bbao

how about the other workstations? can they successfully PING throught the server?

KeatingSimons

ASKER

I'm new to this, is this where I respond to your comment/question? If so, I can ping the server by name or IP, I'm not sure what you mean by ping through the server?

bbao

hehe, sorry for making confusion. what i mean is, can they successfully PING the server form the workstations other than the problematic one?

KeatingSimons

ASKER

yes

bbao

how do you PING the server from the problematic workstation? by IP address? by DNS or NETBIOS name? if you can PING the server by IP address, that should be a name resolution issue.

KeatingSimons

ASKER

I cannot ping the server from the problematic workstation, not by IP, not by name either

bbao

ok, i am wondering if it is a routing related problem. could you please post the "ipconfig /all" and "route print" results of both the server and that problematic workstation? thanks,

KeatingSimons

ASKER

I hate to be stupid, but on the server the results of these commands fill more than the screen and go by too fast to read. Plus there is a tremendous amount of information. Is there a way to print these results to a file?

bbao

hehe, never mind, it is a FAQ :)

just use "ipconfig /all > a.txt" and "route print > b.txt" to log what happens, then paste a.txt and b.txt to here. NOTE: plesae dont overwrite the text log for the server by that of the workstation :)

KeatingSimons

ASKER

Thank you, that's the only thing about this that's been easy.

Results for workstation:

Windows IP Configuration

Host Name . . . . . . . . . . . . : julenew01

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : nuvox.net

Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller

Physical Address. . . . . . . . . : 00-08-74-BF-D1-48

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.0.0.3

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . : 10.0.0.1

DHCP Server . . . . . . . . . . . : 10.0.0.1

DNS Servers . . . . . . . . . . . : 64.89.70.2

Lease Obtained. . . . . . . . . . : Monday, August 23, 2004 4:26:54 PM

Lease Expires . . . . . . . . . . : Monday, August 23, 2004 6:26:54 PM

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 08 74 bf d1 48 ...... Broadcom 440x 10/100 Integrated Controller - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.3        30
10.0.0.0 255.0.0.0 10.0.0.3 10.0.0.3        30
10.0.0.3 255.255.255.255 127.0.0.1 127.0.0.1        30
10.255.255.255 255.255.255.255 10.0.0.3 10.0.0.3        30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1        1
224.0.0.0 240.0.0.0 10.0.0.3 10.0.0.3        30
255.255.255.255 255.255.255.255 10.0.0.3 10.0.0.3        1
Default Gateway: 10.0.0.1
===========================================================================
Persistent Routes:
None

Results for server

Windows NT IP Configuration

      Host Name . . . . . . . . . : sandk01.nuvox.net
      DNS Servers . . . . . . . . : 64.89.70.2
       64.89.70.4
      Node Type . . . . . . . . . : Hybrid

      NetBIOS Scope ID. . . . . . :

      IP Routing Enabled. . . . . : No

      WINS Proxy Enabled. . . . . : No

      NetBIOS Resolution Uses DNS : Yes

Ethernet adapter E100IB6:

      Description . . . . . . . . : Intel(R) InBusiness 10/100 Network Adapter

      Physical Address. . . . . . : 00-90-27-FD-05-B7

      DHCP Enabled. . . . . . . . : No

      IP Address. . . . . . . . . : 10.0.0.2

      Subnet Mask . . . . . . . . : 255.255.255.252

      Default Gateway . . . . . . : 66.83.98.109

      Primary WINS Server . . . . : 10.0.0.2

Ethernet adapter El980n43:

      Description . . . . . . . . : 3Com 3C980 Fast Ethernet Se

      Physical Address. . . . . . : 00-50-04-B1-38-60

      DHCP Enabled. . . . . . . . : No

      IP Address. . . . . . . . . : 66.83.98.110

      Subnet Mask . . . . . . . . : 255.255.255.252

      Default Gateway . . . . . . : 66.83.98.109

PPP adapter NdisWan8:

      Description . . . . . . . . : NdisWan Adapter

      Physical Address. . . . . . : 00-00-00-00-00-00

      DHCP Enabled. . . . . . . . : No

      IP Address. . . . . . . . . : 0.0.0.0

      Subnet Mask . . . . . . . . : 0.0.0.0

      Default Gateway . . . . . . :

PPP adapter NdisWan5:

      Description . . . . . . . . : NdisWan Adapter

      Physical Address. . . . . . : 00-00-00-00-00-00

      DHCP Enabled. . . . . . . . : No

      IP Address. . . . . . . . . : 0.0.0.0

      Subnet Mask . . . . . . . . : 0.0.0.0

      Default Gateway . . . . . . :

PPP adapter NdisWan4:

      Description . . . . . . . . : NdisWan Adapter

      Physical Address. . . . . . : 00-00-00-00-00-00

      DHCP Enabled. . . . . . . . : No

      IP Address. . . . . . . . . : 64.182.137.119

      Subnet Mask . . . . . . . . : 255.255.255.0

      Default Gateway . . . . . . :

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 90 27 fd 05 b7 ...... Intel(R) InBusiness 10/100 Network Adapter
0x3 ...00 50 04 b1 38 60 ...... 3Com 3C980 Fast Ethernet Se
0x4 ...00 00 00 00 00 00 ...... NdisWan Adapter
0x5 ...00 00 00 00 00 00 ...... NdisWan Adapter
0x6 ...00 00 00 00 00 00 ...... NdisWan Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 66.83.98.109 10.0.0.2        1
0.0.0.0 0.0.0.0 66.83.98.109 66.83.98.110        1
10.0.0.0 255.255.255.252 10.0.0.2 10.0.0.2        1
10.0.0.2 255.255.255.255 127.0.0.1 127.0.0.1        1
10.255.255.255 255.255.255.255 10.0.0.2 10.0.0.2        1
64.182.137.119 255.255.255.255 127.0.0.1 127.0.0.1        1
66.83.98.108 255.255.255.252 66.83.98.110 66.83.98.110        1
66.83.98.110 255.255.255.255 127.0.0.1 127.0.0.1        1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1        1
224.0.0.0 224.0.0.0 10.0.0.2 10.0.0.2        1
224.0.0.0 224.0.0.0 64.182.137.119 64.182.137.119        1
224.0.0.0 224.0.0.0 66.83.98.110 66.83.98.110        1
255.255.255.255 255.255.255.255 10.0.0.2 10.0.0.2        1
===========================================================================

bbao

you have mismatched network masks for the workstation and server:

the server's network mask (255.255.255.252) means that only 4 IPs in its 10.0.0.0 subnet, in fact, only two hosts (10.0.0.0.1 and 10.0.0.2) are avialable on in the subnet, 10.0.0.0 is reserved for network segment, 10.0.0.3 is reserved for network broadcasting, but the workstation is using this address!! this makes the two hosts can not reach each other.

the workstation's network mask (255.0.0.0) means that about 16M hosts could be accessible in its subnet. 10.0.0.3 is an usable IP on THIS network, but it is NOT an usable IP for server's subnet.

briefly, the server's subnet is only a small (even mini) part of the workstation's network, but unfortunately, the workstation's IP is even not an usable IP in the pretty small subnet of server.

solution: change the host 10.0.0.1 and 10.0.0.2's network masks to 255.0.0.0. although i dont think you need such a big network mask, but it is the simple way to solve your problem. :)

hope it helps,
bbao

KeatingSimons

ASKER

will that screw up the remaining workstations (7) that are currently working? also, I think I can change the mask on the server, but not on the router. is changing it on the router necessary?

KeatingSimons

ASKER

I've read your suggestion again and am confused about something else, the other workstations are being assigned IPs from 10.0.0.4 through 10.0.0.10. This is more IPs than should be allowed if I understand you correctly?

bbao

you have 7 reamining workstations?! what are their IP addresses? it sounds so strange that they can work well with the servers which reside on a pretty small subnet that supports only 2 workable IPs. i am guessing that the router 10.0.0.1 has a right network mask, so the remaining workstations can access it without problem but not the server 10.0.0.2. or, your router is wroking to route between 10.0.0.0/30 and 10.0.0.4/30?! hehe :)

anyway, plesae list the IP address/mask pairs of your router and those workable workstations one by one. thanks.

KeatingSimons

ASKER

changing the subnet mask for the server IP 10.0.0.2 worked, problem w/station is now functioning properly and I don't seem to have any problems on the remainder of the network. based on what you've said, my network shouldn't be working I guess. workstation IPs range from 10.0.0.3 through 10.0.0.10, subnets are all 255.0.0.0

bbao

glad to hear it works. btw, are you sure that you could PING the server (10.0.0.2) well from the workstations (10.0.0.4 - 10.0.0.10) before changing the server's subnet mask?

KeatingSimons

ASKER

yes, thanks for help!

ASKER CERTIFIED SOLUTION

bbao

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

bbao

KeatingSimons, if you like, you may verify if what i just posted is correct or not. oh, you have to change the server 10.0.0.2's subnet mask back to 255.255.255.252, hehe.

it is quite simple: just ping server 10.0.0.2 from workstation 10.0.0.4. but the constraint is: you must keep the router 10.0.0.1 running; otherwise, you can NOT ping the server from the workstation, although it looks they are locally on same subnet. sounds strange? have a try! :)

regards,
bbao