We are having problems with DHCP and 491 (sp1) clients. The problem
happens getting gateway info from the DHCP server.
With 491, some clients are experiencing not receiving the gateway but can
receive the IP address and subnet mask fine.
Ive tested this with client 49 SP2 and the problem doesnt arise.
The version of DHCP is the ISC DHCPD 3.0.3 (latest version).
NB Clients are XP SP2
Regards,
Someone else has reported a similar issue with client 4.91. Can you verify
it with the base 4.91 client as well?
Has anything else changed recently?
Lets gather some more details about your environment...
Any additional components of the client installed?
What protocols are bound to the client?
Windows Event logs showing anything unusual?
Was Windows installed from scratch, a custom image, or an OEM image?
Security or any other driver-based software like firewall, VPN, remote
management, antivirus, etc. installed and running?
Can you give us any details about the make/model of hardware, NIC and its
drivers, etc. of said workstation?
--
Tony Pedretti
TransUnion Corporation
> Any additional components of the client installed?
Nope. Im leaving off NICI and NMAS. And tried with IP only and IP+IPX,
problem occurs with both
> What protocols are bound to the client?
As above, tried with ip only and ip+ipx
> Windows Event logs showing anything unusual?
> Was Windows installed from scratch, a custom image, or an OEM image?
I can actually replicate it on my own machine. Windows would have been
installed from scratch about 10 months ago. Fully updated with windows
update (even day before yesterdays updates)
> Security or any other driver-based software like firewall, VPN, remote
> management, antivirus, etc. installed and running?
Running Mcafee Virusscan Enterprise 8.0 with latest sdats. Access
protection is a default settings + all unwanted programs policy are
ticked.
Running VNC server 4.1.1
Running bulletproof ftp server 2.3.1 build 26
No firewall enabled
Also running apache for windows
Note DHCP server is on same subnet as me so not ACL problem.
It is also happening to some wireless clients, only a handful.
> Can you give us any details about the make/model of hardware, NIC and
its
> drivers, etc. of said workstation?
Dell Optiplex GX280, 1 gig ram,
NIC - Intel Pro/1000 MT (Driver Version) 7.0.34.0
Connecting in tnrough a Catalyst 2950, then into our core Catalyst 6509
(where all our servers hang off from).
ZENworks 4.x or 6.x agent present on the machines, or can we
categorically rule out the NOVDHCP.DLL-related issues that could
potentially interfere with Windows TCP/IP stack from getting/renewing
its IP address? (TID10091089, TID10090994, TID10093676, etc.)
The address the machines receive is the correct DHCP server-assigned
address, and not the 169.xx.xx.xx APIPA-assigned address? (When
Windows assigns an APIPA address, the gateway is not specified, which
is why I ask.)
Certainly an odd observation. If there isn't a software-level
conflict that can be identified, it may take a LAN trace of the
workstation activity from boot in order to try and make a better guess
at what's happening with regard to the DHCP address and info
assignment.
Any events being registered in the System or Application event logs
regarding a failure of the Windows DHCP server to do something or the
other?
r...@nospam.ie wrote:
Alan Adams
alancru...@drcrumb.com
(for email, remove the crumbs)
Guidelines to Take a Packet Trace
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10011012.htm
How to use Ethereal to capture a packet trace.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10070788.htm
--
Tony Pedretti
Anyway, it is the 4.91e client that this issue is occurring on. It started
happening after I installed a windows domain. I did need to install a dns
server on the windows box. I then set up the domain as a zone on my Netware
dns box. The forwarding is working with windows picking up the Novell box
for forwarding (for internet access). Though, I don't have it right yet. I
can not ping the windows servers by name, though I have added the resources
records.
Anyway, maybe this information will be helpful in troubleshooting why others
are not picking up the default gateway. As I mentioned, until I installed
the domain (client is not a member of the domain), this was not a problem.
I haven't had an opportunity to troubleshoot this yet, so if anyone has any
solutions, let me know. Otherwise, I will post what I come up with.
Thanks,
Janet
<r...@nospam.ie> wrote in message
news:m1p3f.1202$l%3....@prv-forum2.provo.novell.com...
<r...@nospam.ie> wrote in message
news:m1p3f.1202$l%3....@prv-forum2.provo.novell.com...
All of these are Gx620's, windows xp sp2, attaching to a NW6.5 SP3
server. No other workstations are experiencing this problem. I hope
to work with it this weekend.
DHunter
"Why do we work so hard? Because we have products that hardly work!" Former M$ Admin
If anyone has gotten further than this in a solution, please share.
Thanks,
Janet
"D Hunter" <wjjo...@removethis.gmail.com> wrote in message
news:1dgvl15d3qtpusr31...@4ax.com...
Hope this helps,
Thanks for any help,
Brett Kluiber
On Wed, 26 Oct 2005 20:28:18 GMT, "jdw" <jwil...@stlawrencegas.com>
wrote: