My guess is that it is a WINS problem. If the W98 machines are in the
same subnet as the server they can find the server by broadcasting if WINS
lookup fails. If they are in a different subnet, WINS is their only hope.
Do you see an entry in WINS for <domainname 1C> or domainname Domain
Controller? Does it point to the DC's IP address?
In the TCP/IP settings of the W98 machines, are they set to log on to
the Netbios name of your domain? They will use this name to find a DC. They
will send a name request to WINS for this name with the special Netbios
character 1C added (padded to 16 characters) to find the logon server.
"IngenuityTech" <(E-Mail Removed)> wrote in message
news:72FF21EA-AAAD-4B9D-B11B-(E-Mail Removed)...
> Thanks for the reply Bill,
>
> In regards to WINS all machines are receiving it by means of DHCP. They
> receive both primary and secondary WINS servers whic are located on the
> 10.
> network.
>
> I understand that 98 machines don't join domains and that they are usually
> ready to go after putting in necessary domain info into MS Client and
> Identifcation under Network Properties.
>
> What seems odd to me is that when the 98 machine is within the 192. net it
> cannot log in to the domain but when inside the 10. net in can log in.
> WINS
> is provided under both DHCP scopes along with DNS server and router info.
> XP
> machines obviously have no problem because they receive DNS under both
> scopes.
>
> "Bill Grant" wrote:
>
>> Those things are not related to routing. All that routing does is
>> give
>> you an IP connection. If a machine can ping the other machine by its IP
>> address, routing is working. Your problems are probably caused by the
>> fact
>> that you are in a routed network, and routers do not allow broadcasts to
>> pass. Are all machines set to use WINS?
>>
>> Windows 98 machines cannot join a domain. Joining a domain means that
>> the client computer registers with the domain controller and sets up a
>> secure communication channel. W98 cannot do this.
>>
>> Users on W98 machines can log on to their domain accounts but they
>> will
>> use the Netbios special name <domainname 1C> to find the domain
>> controller.
>> They do not log on using DNS like XP clients. WindowsNT servers used
>> Netbios
>> for this, and W98 was designed to work with NT servers. Active Directory
>> was
>> still a couple of years in the future.
>>
>> "IngenuityTech" <(E-Mail Removed)> wrote in
>> message
>> news:7B824FCB-B3B2-49D1-9617-(E-Mail Removed)...
>> > Setup:
>> >
>> > Windows 2003 Server with SP1
>> > - Two Network Cards
>> > - Running DHCP, RRAS, NAT
>> >
>> > Network Card 1 (Connects to Managed Switch 1)
>> > IP: 10.191.1.25 (Static)
>> > SM: 255.255.255.0
>> > DG: 10.191.1.1
>> >
>> > DHCP Providing to Clients on Network 1:
>> > IP: 10.191.1.1 - 10.191.1.254
>> > SM: 255.255.255.0
>> >
>> > Network Card 2 (Connects to Unmanaged Switch 2)
>> > IP: 192.168.6.1 (Static)
>> > SM: 255.255.255.0
>> > DG: None
>> >
>> > DHCP Providing to Clients on Network 2:
>> > IP: 192.168.6.1 - 192.168.6.254
>> > SM: 255.255.255.0
>> >
>> > Network 1 clients connect to a managed switch which in turn connects
>> > to
>> > the corporate network (Active Directory) and the internet. No
>> > problems
>> > connecting/browsing/joining domain with either XP or 98 machines.
>> >
>> > Network 2 clients connect to an unmanaged switch which is used
>> > primarily
>> > for Ghost imaging, pc setup and needs to join domain. XP Machines have
>> > no
>> > problem connecting/browsing/joining domain with the exception of 98
>> > machines.
>> >
>> > I have RRAS/NAT installed to allow traffic to pass between the
>> > networks.
>> >
>> > Problem:
>> >
>> > XP Machines need to have full dns suffix supplied to allow joining of
>> > domain.
>> > 98 Machines can get an ip but cannot log onto domain.
>> >
>> > Could I have the routing setup incorrectly? Do I need a static route?
>> > Any help would be appreciated.
>> >
>> >
>>
>>
>>
|
Similar Threads
Linear Mode
