We have our network subnetted that way to provide two broadcast doamins of
1022 hosts each.  This is not an improper method of subneting for two
networks.  We just use large networks.  This best suites our organizational
needs and has worked for over five years.  The problem regarding our NT
authentication is new and I suspect it is being caused by a third party on
our network.  Possibly someone running some services they shouldn't be.
Thanks,
John

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 4:01 PM
To: Exchange Discussions
Subject: RE: Problems Logging on to domain.


This is an improper subnet for only 2 networks.  Your using a class B
network and 6 bits from the third octet (252).  This would yield 62 subnets
with 1022 hosts per subnet and a range of 4.  (Check my math everyone).

Why not just close off all the bits for each subnet.  Example:
172.22.64.0
255.255.255.0

and

172.22.32.0
255.255.255.0

This gives you two networks of 254 hosts each.

-----Original Message-----
From: Wynkoop, John [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 2:50 PM
To: Exchange Discussions
Subject: OT: Problems Logging on to domain.


I'm having some serious problems with my NT domain, have exhausted all my
resources, and don't know where else to look... any help would be
appreciated.  

Symptoms:

My windows 98 clients on a different subnet are unable to log on to the
domain.  (they are on the 172.22.64.0/255.255.252.0 subnet)   My domain
controllers and WINS servers are on the 172.22.32.0/255.255.252.0.  When
anyone tries to log in they get a message saying that "The domain password
you supplied is not correct or access to your logon server has been denied."
However, when I use the same credentials on the 172.22.32.0/255.255.252.0
subnet, I can log in with no problems.  The computers on the
172.22.64.0/255.255.252.0 subnet can log in to another domain which has it's
domain controllers on that subnet.  I've also noticed that the problem
computers (the one's on the 172.22.64.0/255.255.252.0 subnet) can not use
WINS to look up the PDC (strange), but can ping it's IP and use DNS to
resolve it's name.  However, this doesn't seem to affect all computers on
that subnet... At this point I'm at my wits end... :(

System Info:

All workstations thus far have been Win98

All of my domain controllers are NT 4 running SP5 or higher...

Event logs for DC's show no failed or successfull log on attempts for any of
the users
that are trying to log in from the affected workstations.

All workstations can use TCP/IP fine, but have problems when trying to use
netbios to contact my PDC.

This worked until last week sometime with no problems, the only thing that's
changed is that the PDC
was on ATM with only one elan and is now on Ethernet (Shouldn't have made
any differance, they are
essentially the same thing).

Thanks,
John

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to