machine unable to access the network

  • Thread starter Thread starter Penny
  • Start date Start date
P

Penny

I've got a user who can see the network, but can't access it. He's got a LOT
of Dhcp 1002 errors and at the onset of the problem got a netlogon 5719
error. While trying to look these errors up in here it didn't come up with
any results.

I tried all the usual reloading of the drivers, ipconfig/renew, and the
ususal stuff and am coming up empty. DHCP is denying him. If anyone can
help me with this I would REALLY appreciate it.
 
More info on this machine. It can see the Novell stuff, but can't see the
network as a whole. That's the part that puzzles me so much. It can even
see the network shares, but once I click on it it's inaccessable.

I really don't uderstand this one, usually when there's problems like this,
updating the driver usually does the trick. I've also tried uninstalling the
microsoft network stuff, and then reinstalling them, which didn't work.

I haven't ever worked in an environment where there's both Novell and Active
directory, it's proven to have it's challanges. This is my first week in
this new position, so I need to start doing my homework on how the 2 play
together.

It's apparent there's nothing wrong with the card, nor the network line,
otherwise the user wouldn't even be able to see the Novell related things, in
truth I haven't EVER worked with it in an administrative position, I was just
a user back in 1986 and I was aware that we were on a Novell network.

I believe this to be a DHCP problem, I also tried renaming the machine, then
try to rejoin it to the domain with no success.

I'm out of options. I honestly don't know what else to try. Please if
anyone knows what I can do to remedy this problem, please get back to me!

I had a similar problem earlier this week with another machine, but it was
an XP machine. They use entirely different software than I'm familiar with.
For Virus protection, they're using Trend Micro. anyways this other machine
had a scanner attached too it, and it had the Trend Micro scanner software in
the startup, once I removed that Using msfoncig, things started to change. I
shut it all the way down and suddenly it could see the network again.

The reason I'm mentioning this is because the machine I'm having issues with
also has something from Trend Micro fire up in the startup, but I only saw it
once in the many times I've rebooted it. I am familiar with MSCONFIG in XP,
but it isn't the same command in window 2000. I really think if I can take
that program out of the startup, that is a step in the right direction. How
do you take things out of the startup in Windows 2000? I really thought it
was the same command, but apparently it's not.

At any rate, NONE of the obvious things are working for me. I really need
some assistance. With all the elements I'm not dealing with here, that I'm
not used to dealing with, that throws a LOT of variables into the mix.

Before starting with this position on Monday of this week, I had little to
go on as far as what systems they had running, and I'm shocked to have to
deal with Novell and the netuse command again. Setting up users is also a
HUGE deal when it really shouldn't be. It's all because of this Novell
system. The AD DC doesn't replicate amoungst the other servers. The DC is
on windows 2003, yet it's got the hodge podge of Novell, and some Linux
servers too. I've somehow got to find out what can be upgraded, so we can
take some steps out of the this equation.

I walked into a really challanged situation. The last position I held was
similar too it, and it took me 3 years to work it out. I'd like to think
that I made a difference, but by the time I was finished I was very burned
out. I know, but until I start sifting these machines, which all can be
upgraded to XP, have to deal with the machines with older OS's for the
interum. I had a process of re-imagineing machines in the old job, which I
hope to learn an entire process with in this job.

I have many other challanges to work out, but would be very happy to get
some suggestions given this new information. I hope it is helpful.
 
If you need fast answers a message group is not the place to go. There may
be a 24 hour turnaround for every post and every reply you make. You should
be seeking local help,...possibly even someone who can physically come there
and help.

Penny said:
I believe this to be a DHCP problem, I also tried renaming the machine,
then
try to rejoin it to the domain with no success.

Go into the DHCP Active Lease List and delete the entry for that machine.
Let it create a new one by itself.
I had a similar problem earlier this week with another machine, but it was
an XP machine. They use entirely different software than I'm familiar
with.
For Virus protection, they're using Trend Micro. anyways this other
machine
had a scanner attached too it, and it had the Trend Micro scanner software
in
the startup, once I removed that Using msfoncig, things started to change.
I
shut it all the way down and suddenly it could see the network again.

Leave the Trend Micro alone.
The only exception would be if Trend Micro includes some sort of "Personal
Firewall". In which case you would uninstall Trend Micro and then reinstall
it with the Anti-Virus only and don't include the "firewall" component.

DHCP 1002 is not a specific error with only one cause,...it is worthless to
me without the entire text of the error.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
 
There is not a listing for this machine in DHCP.

The message reads IP Address lease 0.0.0.0 for network card address was
denied by DHCP, the server sent back a DHCPNACK message.

If I try to ipconfig/renew I get "Unexpected network failure or
iinsufficient access.
 
Give it a statically assigned TCP/IP configuration to see if the machine is
even capable of functioning on the LAN.

If it does work that way, then run it that way until you can call MS to get
a real solution,...if it still doesn't work then you need to troubleshoot
from that persepctive which includes the physical cabling and good/bad
network hardware.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
 
Back
Top