win98clients & win2k server

Hello,

I have 2 classes whith win98 clients, the clients worked fine until I
installed dns, wins a dhcp on my mainserver so I could work wtih only one
server(before those services were on a small win2003server).
All the other classes work fine(all WinXp clients), but my win98 clients
can't find a valid domainserver to logon to.
The Ip-adress of the main server is the same, the dns server has also the
same ip as before, and I didn't change the settings in the network config.
Can anyone tell my what the problem can be?

Thanks,
Nico.

Make sure the Win98 machines are getting the right WINS entry, they won't be
able to find the DC without it. Also make sure that all machines involved
have "Netbios over TCP/IP" enabled.

You should also make sure the rest of their networks settings are correct,
such as their Default Gateway. If they receive all this from DHCP then use
"Winipcfg" with all options visible to verify what they receive.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"nico" <(E-Mail Removed)> wrote in message
news:OZAY%(E-Mail Removed)...
> Hello,
>
> I have 2 classes whith win98 clients, the clients worked fine until I
> installed dns, wins a dhcp on my mainserver so I could work wtih only one
> server(before those services were on a small win2003server).
> All the other classes work fine(all WinXp clients), but my win98 clients
> can't find a valid domainserver to logon to.
> The Ip-adress of the main server is the same, the dns server has also the
> same ip as before, and I didn't change the settings in the network config.
> Can anyone tell my what the problem can be?
>
> Thanks,
> Nico.
>
>

I checked the settings and they seem to be correct.
I get the settings from dhcp(ip, dns, gateway & wins).
If I check my dns-server, the win98 clients are not in it, they do appear in
my dhcp-server.

So the DC is still not reachable for win98 clients, I think it has something
to do with a setting on my Server because that is the one that has changed.
I have know 2 nic's instead of one before......the new one is for dns, wins
& dhcp
I think I checked almost everything, if you have another suggestion, shot
away.

Greetings,
N

"Phillip Windell" <@.> schreef in bericht
news:(E-Mail Removed)...
> Make sure the Win98 machines are getting the right WINS entry, they won't
be
> able to find the DC without it. Also make sure that all machines involved
> have "Netbios over TCP/IP" enabled.
>
> You should also make sure the rest of their networks settings are correct,
> such as their Default Gateway. If they receive all this from DHCP then
use
> "Winipcfg" with all options visible to verify what they receive.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> "nico" <(E-Mail Removed)> wrote in message
> news:OZAY%(E-Mail Removed)...
> > Hello,
> >
> > I have 2 classes whith win98 clients, the clients worked fine until I
> > installed dns, wins a dhcp on my mainserver so I could work wtih only
one
> > server(before those services were on a small win2003server).
> > All the other classes work fine(all WinXp clients), but my win98 clients
> > can't find a valid domainserver to logon to.
> > The Ip-adress of the main server is the same, the dns server has also
the
> > same ip as before, and I didn't change the settings in the network
config.
> > Can anyone tell my what the problem can be?
> >
> > Thanks,
> > Nico.
> >
> >
>
>

You can't run two nics like that. You can not specify a certain nics for
"dns, wins & dhcp". The purpose of two nics is when each one is tied to a
different subnet for Layer3 purposes, however Domain Controllers should only
have one nic and use *other* servers for multi-homing. SBS is the only
exception where it is expected to be duel-homed. Take out the second nic and
run only one nic,...be sure to delete the "Connection" and the Nic Device
first before removing the physical nic.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"nico" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I checked the settings and they seem to be correct.
> I get the settings from dhcp(ip, dns, gateway & wins).
> If I check my dns-server, the win98 clients are not in it, they do appear
in
> my dhcp-server.
>
> So the DC is still not reachable for win98 clients, I think it has
something
> to do with a setting on my Server because that is the one that has
changed.
> I have know 2 nic's instead of one before......the new one is for dns,
wins
> & dhcp
> I think I checked almost everything, if you have another suggestion, shot
> away.
>
> Greetings,
> N
>
> "Phillip Windell" <@.> schreef in bericht
> news:(E-Mail Removed)...
> > Make sure the Win98 machines are getting the right WINS entry, they
won't
> be
> > able to find the DC without it. Also make sure that all machines
involved
> > have "Netbios over TCP/IP" enabled.
> >
> > You should also make sure the rest of their networks settings are
correct,
> > such as their Default Gateway. If they receive all this from DHCP then
> use
> > "Winipcfg" with all options visible to verify what they receive.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> > "nico" <(E-Mail Removed)> wrote in message
> > news:OZAY%(E-Mail Removed)...
> > > Hello,
> > >
> > > I have 2 classes whith win98 clients, the clients worked fine until I
> > > installed dns, wins a dhcp on my mainserver so I could work wtih only
> one
> > > server(before those services were on a small win2003server).
> > > All the other classes work fine(all WinXp clients), but my win98
clients
> > > can't find a valid domainserver to logon to.
> > > The Ip-adress of the main server is the same, the dns server has also
> the
> > > same ip as before, and I didn't change the settings in the network
> config.
> > > Can anyone tell my what the problem can be?
> > >
> > > Thanks,
> > > Nico.
> > >
> > >
> >
> >
>
>

Ok,

it works now, I reinstalled my dchp, I probably screwed something up there.
The win98clients are up and running again.

About the multiple nic's, someone has told me it is a good idea to use
different nic's for diferent service's like I did now for dhcp,dns & wins 1
nic and for all the rest another nic.
Why is this not a good idea?

Thanks.
Nico.

"Phillip Windell" <@.> schreef in bericht
news:#(E-Mail Removed)...
> You can't run two nics like that. You can not specify a certain nics for
> "dns, wins & dhcp". The purpose of two nics is when each one is tied to a
> different subnet for Layer3 purposes, however Domain Controllers should
only
> have one nic and use *other* servers for multi-homing. SBS is the only
> exception where it is expected to be duel-homed. Take out the second nic
and
> run only one nic,...be sure to delete the "Connection" and the Nic Device
> first before removing the physical nic.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "nico" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I checked the settings and they seem to be correct.
> > I get the settings from dhcp(ip, dns, gateway & wins).
> > If I check my dns-server, the win98 clients are not in it, they do
appear
> in
> > my dhcp-server.
> >
> > So the DC is still not reachable for win98 clients, I think it has
> something
> > to do with a setting on my Server because that is the one that has
> changed.
> > I have know 2 nic's instead of one before......the new one is for dns,
> wins
> > & dhcp
> > I think I checked almost everything, if you have another suggestion,
shot
> > away.
> >
> > Greetings,
> > N
> >
> > "Phillip Windell" <@.> schreef in bericht
> > news:(E-Mail Removed)...
> > > Make sure the Win98 machines are getting the right WINS entry, they
> won't
> > be
> > > able to find the DC without it. Also make sure that all machines
> involved
> > > have "Netbios over TCP/IP" enabled.
> > >
> > > You should also make sure the rest of their networks settings are
> correct,
> > > such as their Default Gateway. If they receive all this from DHCP
then
> > use
> > > "Winipcfg" with all options visible to verify what they receive.
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > > "nico" <(E-Mail Removed)> wrote in message
> > > news:OZAY%(E-Mail Removed)...
> > > > Hello,
> > > >
> > > > I have 2 classes whith win98 clients, the clients worked fine until
I
> > > > installed dns, wins a dhcp on my mainserver so I could work wtih
only
> > one
> > > > server(before those services were on a small win2003server).
> > > > All the other classes work fine(all WinXp clients), but my win98
> clients
> > > > can't find a valid domainserver to logon to.
> > > > The Ip-adress of the main server is the same, the dns server has
also
> > the
> > > > same ip as before, and I didn't change the settings in the network
> > config.
> > > > Can anyone tell my what the problem can be?
> > > >
> > > > Thanks,
> > > > Nico.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

"nico" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> About the multiple nic's, someone has told me it is a good idea to use
> different nic's for diferent service's like I did now for dhcp,dns & wins
1
> nic and for all the rest another nic.
> Why is this not a good idea?

I have no idea why they think it is a good idea,..I think it is a bad idea.

It screws up the Layer3 functions of the OS since there is no "distinction"
that the OS can use to know which physical NIC to route out of,....layer3
routing is subnet-to-subnet, not host-to-host, and both your nics would be
in the same subnet. At least that is the "broad generality" of it, there
are exceptions,....like playing with the priority order and the "bindings"
of the nics to create a distinction between them. You are better off
adding multiple IP#s to the same physical NIC when they are in the same
subnet. But then even after all that, you still have to have a method to
cause the dhcp, dns, and wins to only use one of the specified IP#s. I have
not seen a way to do that, although I must admit I have never been
interested in doing so and haven't looked into it. Packet filters can do
this artificially at a different level, but that doesn't help the OS decide
what to do.

Now things like IIS can bind certain websites to certain IP#s and would work
fine and may even work fine with multiple physical NICs, but here you are
dealing with an Applications or Services that has been designed to work this
way.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Tx for all your feedback Phillip, it has been helpfull to me.

Greetings,
Nico.



"Phillip Windell" <@.> schreef in bericht
news:(E-Mail Removed)...
> "nico" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > About the multiple nic's, someone has told me it is a good idea to use
> > different nic's for diferent service's like I did now for dhcp,dns &
wins
> 1
> > nic and for all the rest another nic.
> > Why is this not a good idea?
>
> I have no idea why they think it is a good idea,..I think it is a bad
idea.
>
> It screws up the Layer3 functions of the OS since there is no
"distinction"
> that the OS can use to know which physical NIC to route out of,....layer3
> routing is subnet-to-subnet, not host-to-host, and both your nics would be
> in the same subnet. At least that is the "broad generality" of it, there
> are exceptions,....like playing with the priority order and the "bindings"
> of the nics to create a distinction between them. You are better off
> adding multiple IP#s to the same physical NIC when they are in the same
> subnet. But then even after all that, you still have to have a method to
> cause the dhcp, dns, and wins to only use one of the specified IP#s. I
have
> not seen a way to do that, although I must admit I have never been
> interested in doing so and haven't looked into it. Packet filters can do
> this artificially at a different level, but that doesn't help the OS
decide
> what to do.
>
> Now things like IIS can bind certain websites to certain IP#s and would
work
> fine and may even work fine with multiple physical NICs, but here you are
> dealing with an Applications or Services that has been designed to work
this
> way.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>