ROUTING ISSUE: NT4.0 VS 2000 SERVER

[CARMEN]

I had a NT 4.0 on my network which the default gateway was
pointing to the linksys router and i had changed the
routing table to point my companys router and that worked
fine. I just installed a 2000 server with DNS
configured. The server is able to get out to the linksys
and is able to recognize the other router, but the client
pc's which is a 98 and 2000 pc's are unable to to get
out. they are only able to see the new server.
Can someone please help

Thanks!

 

[Herb Martin]

It would help if you gave a more precise description of the setup
but especially the IPConfig display of the client settings.

Do you perhaps have the client "default gateway" set to the wrong
address (or an internal one)?

What happens when you tracert?

 

[Cpenna]

The setup has the default gateway to 192.168.1.1
(internet) same as the NT was. The routing Table is set
to point to the companys ip router. When i tracert from a
clients pc it says request timed out and each terminal
looks to the IP of the SERVER as there default gateway.
the server handles all request.

 

[Herb Martin]

The setup has the default gateway to 192.168.1.1

(internet) same as the NT was. The routing Table is set
to point to the companys ip router. When i tracert from a
clients pc it says request timed out and each terminal
looks to the IP of the SERVER as there default gateway.
the server handles all request.

Well, is the server a ROUTER?

 

[Guest]

yes the server is a acting as the router.

-----Original Message-----


Well, is the server a ROUTER?

--
Herb Martin



.

 

[Marina Roos]

Is WINS installed on the W2K-server? W9x, ME and NT4 will need it. Also
options 003, 006, 015, 044 and 046 (0x8) need to be set in DHCP-server,
Scope options.
How many nics in the W2K-server?

Marina

 

[Guest]

Marina there is only one nic card and wins isnt installed
on the server. and dhcp server is not enabled they have
static ip.

 

[carmen]

yes the server is a acting as the router.

-----Original Message-----
yes the server is a acting as the router.

.

 

[Marina Roos]

WINS should be installed. Also, it is much better to use DHCP, because it
will push out all the other settings like WINS and DNS too.
DNS on your servernic is pointing to your server-IP, right?

Marina

 

[Herb Martin]

Why are you focuses on the likely irrelevant WINS server issue?

WINS servers are usually unnecessary on a SINGLE segment LAN.

WINS is necessary for NetBIOS resolution when there are multiple
segments (subnets).

 

[CARMEN]

yes the dns is pointing to my server ip... how would i go
about this without using wins and DHCP...? Can this be
done throught DNS?

 

[Herb Martin]

yes the dns is pointing to my server ip... how would i go

about this without using wins and DHCP...? Can this be
done throught DNS?

The WINS recommendation is likely bogus.

WINS is needed when you have multiple subnets and need to
resolve legacy names -- quite common but seems unrelated to your
problems.
[/QUOTE]

 

[CARMEN]

HOW BOUT

if i change the DNS server to the DNS of the isp would
that resolve the issue of the clients accessing the
internet? And if so i would have to change the dns
setting on all the clients 98's and 2000? that should be
resolved by the DNS server.
what do u think?

 

[Herb Martin]

if i change the DNS server to the DNS of the isp would

that resolve the issue of the clients accessing the
internet? And if so i would have to change the dns
setting on all the clients 98's and 2000? that should be
resolved by the DNS server.
what do u think?

I think you would be able to resolve the internet but Win2000
(and perhaps other) internal clients and DCs will not work correctly.

Don't flail about trying different things without understanding the
implications -- figure out the problem and simply correct it.

What is your current problem --specifically -- and how are you
machines configured?

(Ipconfig, ping, tracert, DCDiag, and NetDiag are your friends --
perhaps NSLookup too.)

 

[Guest]

Mr. Martian,
My problem is this origanally i had a NT network with 2000
and 98 clients. The Client Pc's had the default gateway
with 192.17.5.29 (server address) and they are STATIC IP.

NT example servername(water1)
ip:192.17.5.29
subnet:255.255.255.224
defaultgateway:192.168.1.1 (isp)
I had changed the routing table to establish a connection
to my other router i had on the network. which works!!

Now i have a 2000 server with the same client pc's.

2000 server
ip:192.17.5.29
subnet:255.255.255.224
defaultgateway:192.168.1.1
prefered dns:192.17.5.29
had also changed the routing table same as NT.

DNS SERVER: (water1) 192.17.5.29
forwarder: 192.20.1.23
do not use recursion is checked

So what im thinking is changing the DNS SERVER ip address
to the Dns of my isp how would that work?

I greatly appreciate your assistance to this issue if my
explantion is nt good enough please let me know what else
would help you.

Client Pc's can see the SERVER but are unable to ping
192.168.1.1 and the other router that i had put into the
routing table. I havnt tried NSLOOKUP nor did i try to
resolve IP by name.

 

[Marina Roos]

Again, if you have W9x, ME or NT4-clients, WINS needs to be installed on the
server. You can't get it done through DNS. Only W2K/XP understand and rely
completely on DNS. The other OS's need WINS. With the Scope options in
DHCP-server, you can control WINS and DNS to be pushed to the clients.

Marina

 

[Marina Roos]

No Carmen,

That will make things worse.
Put DNS, WINS and DHCP on your server.

Marina

 

[Marina Roos]

Sorry Herb, but you're wrong here.
W2K and XP totally rely on DNS. W9x, ME and NT4 totally rely on WINS.

Marina

 

[Herb Martin]

As I told you in answer to your private email to me the clients
and gateway are not on the same subnet.

Correct your addresses -- don't mess around with DNS until you
fix the routing.

 

[Herb Martin]

Sorry Herb, but you're wrong here.
W2K and XP totally rely on DNS. W9x, ME and NT4 totally rely on WINS.

No, that isn't true in general and isn't relevant to his problem.

While older (legacy) clients tend to prefer or even require NetBIOS
resolution,
WINS is only one of three major ways to resolve NetBIOS:

1) WINS server
2) Broadcasts
3) LMHosts

For a single subnet, broadcasts work just fine. For multiple subnets you
normally
WILL need WINS or an LMHOSTS file.

DHCP is only needed if you wish to assign addresses automatically and while
it
might be a useful addition, it isn't relevant to repairing the problems HE
HAD NOW.

Don't complicate a setup that isn't working with irrelevant additions and
don't flail
around adding things like WINS that won't help.

He has a routing problem as evidenced by his addressing above.