How clients login to server?

[Andrea Moro]

Imagine this scenario: a lot of clients that has a
default gateway that is a ADSL router that let them
go on internet.

Clients can logon to server, because before to set up
as default gateway the router it was the server with
a dns ... so clients log on because they have the
login info stored into cache ... but when they have
logged in, in network resource they cannot access
anymore to the server.

Clients return back error "machinename isn't accessible".

What's happening? Ping works to and from both
machine (clients and server) ... but on server network
resources apper empty ... no machine are displayed
into.

Hope anyone can help me.

Andrea

 

[Herb Martin]

Imagine this scenario: a lot of clients that has a
default gateway that is a ADSL router that let them
go on internet.

Clients can logon to server, because before to set up
as default gateway the router it was the server with
a dns ... so clients log on because they have the
login info stored into cache ...

Logon in what sense? Is this machine a Windows machine?
What type? Domain or server account?

(They likely don't logon to it in any case -- they might/probably
AUTHENTICATE)

Cache what? DNS is not a logon which is the normal thing
to find in cache for such situations....

Cached authentication credentials do NOT work on the
network usually (by design.)

logged in, in network resource they cannot access
anymore to the server.

What does any of this have to do with the ADSL?

Access how? What symptoms do you actually get?
What specifically works and doesn't work?

Can you ping? By name? By only IP? Can you
What resource are you trying to use?

Clients return back error "machinename isn't accessible".

Return back from WHAT TYPE of access?

Net View \\servername\sharename
(What do you get?)

What's happening? Ping works to and from both
machine (clients and server) ... but on server network
resources apper empty ... no machine are displayed
into.

By name or just by number?

 

[Andrea Moro]

Uau ... too much question....

I'll try to reply all.

Logon in what sense? Is this machine a Windows machine?
What type? Domain or server account?

There is a domain server, there are some clients.
Clients try to authenticathe them throught logon form
that appear just after windows is started up.

Cache what? DNS is not a logon which is the normal thing
to find in cache for such situations....

Cache login information. Haven't y never experienced
of a domain server unreachable and clients use previous
login information (credential) stored on the client?

Cached authentication credentials do NOT work on the
network usually (by design.)

All times I've some problem on antoher network environment
and server isn't unreachable ... I can login in the clients
(using last username/password) and w2k let me enter in.

What does any of this have to do with the ADSL?

Browse internet, download e-mail ...

Access how? What symptoms do you actually get?
What specifically works and doesn't work?
Can you ping? By name? By only IP? Can you
What resource are you trying to use?

Ping .,.. tried only by ip ... not anything else.

When I double click on computer name under network
resource available for those domain I get back an alert
message box with the attention symbol and a message
saying "machine name isn't unreachable".
That's all.

Net View \\servername\sharename
(What do you get?)

I didn't tried it.

See before.

Andrea

 

[Sartan Dragonbane]

Try setting up a WINS proxy for dhcp & dns.

 

[Herb Martin]

Uau ... too much question....

That's how you troubleshoot. You ask SPECIFIC
questions until you isolate the problem.

Fixing problems is easy -- finding them is a bit harder.

There is a domain server, there are some clients.
Clients try to authenticathe them throught logon form
that appear just after windows is started up.

Ok, so this doesn' t have much to do with your DSL or
gateway does it?

Is so, is the router (gateway) between the clients and the
server?

"Domain server"? Member server or DC?

ALMOST ALL authentication problems in Win2000+ domains
with Win2000+ clients are DNS issues.

IS your DNS dynamic? Is the DC AND the Client configured
to use that same DNS server and NO OTHER?

Cache login information. Haven't y never experienced
of a domain server unreachable and clients use previous
login information (credential) stored on the client?

Cached credentials are for when laptops are "out of the
office" -- they do not provide access to server resources
on the network.

All times I've some problem on antoher network environment
and server isn't unreachable ... I can login in the clients
(using last username/password) and w2k let me enter in.

Yes, you can LOGIN to that same client -- if you have been
there before and the client is caching (it can be turned off)
but you will have little or no access to "network resources"
if you don't get a fresh authentication.

Browse internet, download e-mail ...

Not related to the logon or authentication problems
unless you are using Proxy Server or IAS etc.

It might be another symptom of DNS being wrong.

1) DNS must be dynamic for AD domains
2) ALL clients must be configured to use ONLY internal,
dynamic DNS server (set)
3) DCs are clients too -- see #2
4) DNS may forward to the ISP etc DNS for resolving the Internet

Restart DC's NetLogon process if you have to fix the above.

Ping .,.. tried only by ip ... not anything else.

Ping requires no authentication. You still haven't said
whether you can ping by NAME and not just IP.

Be more picky and more specific when troubleshooting.

When I double click on computer name under network
resource available for those domain I get back an alert
message box with the attention symbol and a message
saying "machine name isn't unreachable".

That's a DNS symptom but you should work mostly
from the command line when you troubleshoot.

 

[Herb Martin]

Try setting up a WINS proxy for dhcp & dns.

WINS proxy does NOTHING for "DHCP" nor
for "DNS".

WINS proxies help non-WINS clients resolve
NetBIOS names from the WINS server that the
non-WINS client cannot resolve through broadcasts.

 

[Sartan Dragonbane]

bleh, i knew that ~~ After i posted.
d'oh.

WINS proxy does NOTHING for "DHCP" nor
for "DNS".

WINS proxies help non-WINS clients resolve
NetBIOS names from the WINS server that the
non-WINS client cannot resolve through broadcasts.

 

[Herb Martin]

bleh, i knew that ~~ After i posted.
d'oh.

I just hate it when I do that <grin>

 

[Andrea Moro]

Well I could try to troubleshoot only on tuesday.
Meanwhile server is a DC... before some little
unconfiguration all works fine ... but because two
clients w98 cannot login to the domain I must
stop some services, and change some configuration.

So ... before of this all was working fine. Dns, wins.
Dhcp no because of two network card cannot release
address correctly.

I suppose that there is wrong information into cache
and just with a nbtstat -rr I can solve ... but I'll know
it only next week.

For the moment I can say y only thanks for your help.
Have a nice weekend and a good easter if y believe
in it.

Andrea

 

[Herb Martin]

Well I could try to troubleshoot only on tuesday.
Meanwhile server is a DC... before some little
unconfiguration all works fine ... but because two
clients w98 cannot login to the domain I must
stop some services, and change some configuration.

You could also try getting someone else to read your
posts for clarity before you hit send.

"must stop some services and change..." sounds like
you are flailing around rather than isolating the problem
and resolving.

Typical tyro mistake.

So ... before of this all was working fine. Dns, wins.
Dhcp no because of two network card cannot release
address correctly.

What do you mean here? There is no special issue with
DHCP releasing addresses that I have ever heard.

Do you have a reference to that in the KB?

I suppose that there is wrong information into cache
and just with a nbtstat -rr I can solve ... but I'll know
it only next week.

Unlikely unless you have a (basic) configuration mistake.

Like multiple WINS servers which are NOT replicating.

You need to clarify your problem - certainly for us to
help - and probably for you to even understand it yourself.

 

[Andrea Moro]

You could also try getting someone else to read your

posts for clarity before you hit send.

"must stop some services and change..." sounds like
you are flailing around rather than isolating the problem
and resolving.

Typical tyro mistake.

I know, but when y plan an installastion thats ends with
no problem, all works fine ... but at one point just two
clients (w98) doesn't want to want in any manner ...
and y are installing the server in a production environment
where every stop-minute is money losed ...
I think y try to flaily problem instead isolated it.

What do you mean here? There is no special issue with
DHCP releasing addresses that I have ever heard.

Do you have a reference to that in the KB?

No, just a supposition.


Well ... last condition for which I plan to restore back all
as it was ... were a w2k adv server, unpromoted to a standalone
server first, then to a standalone clients where no connection
to machine via netbios were allowed.
Apparentely there wasn't reason for which it has done it ... but
I detacthed it definetively from the network and reinstalled a
single client with data hd of server.

Thank y for y help again.
Andrea