[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pw95ift

Title:	PATHWORKS for Windows 95
Notice:	PWW95 1.0A Available -- See notes 3.39 and 8.7
Moderator:	JAMIN::SYSTEMROM

Created:	Thu Nov 17 1994
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	646
Total number of notes:	2900

626.0. "Win95 PW problem with DHCP ?" by KAOT01::M_GREEN () Mon Mar 10 1997 16:49

    Folks,
    wondering if anyone else has seen this problem.   I have two reported
    cases now where customer's implement Pathworks Win95 1.0a (with eco2)
    and their native TCP/IP support fails as a result.  Both customers are
    implementing IP addresses by way of Win NT DHCP servers.  
    
    When the configuration features netbeui / ip  alone, then everthing is
    fine.  The IP address is correctly claimed and all network interaction
    is flawless.  upon inclusion of Pathworks for Win95 1.0a, IP refuses to
    properly start up.   The resulting error message states:
    
    "The system has detected an conflict with the IP address with the system
     having hardware address 08-00-34-00-00.  The interface has been
     disabled."
    
    
    
    The hardware is standardized upon Compaq & 3com 3c509b. The clients are
    running Windows 95.  The Pathworks server is running 5.0D eco 3. 
    
    What is Pathworks Decnet doing to modify an IP parameters beyone
    setting station address??   The winipcfg shows a proper IP lease with
    respective station address, even thought the interface (protocol) is
    not starting up ??  weird huh ??
    
    
    Mike Green
    Pathworks Support 
    Hull CSC

T.R Title User Personal
Name Date Lines

626.1 SPELNK::curless Wed Mar 12 1997 14:04 15

T.R	Title	User	Personal Name	Date	Lines
626.1		SPELNK::curless		`Wed Mar 12 1997 14:04`	15
	Humm... I wonder if this has ANYTHING to do with the fact that installing DECnet causes the hardware address (well... the station address, but then that LOOKS like the hardware address was changed...) from what it used to be to the AA-00-04-00-xx-yy format. Other than that... NO change to thet IP Parameters. I suspect you might have to revoke the IP lease, install, then enable TCP/IP. Also, for sanity check to make sure there are no duplicate DECnet node addresses on the network. All you need is for a duplicate running TCP/IP as well. (Which is what it looks like by the way). Jeff

Humm... I wonder if this has ANYTHING to do with the fact that installing
DECnet causes the hardware address (well... the station address, but then
that LOOKS like the hardware address was changed...) from what it
used to be to the AA-00-04-00-xx-yy format.

Other than that... NO change to thet IP Parameters.  I suspect you might have
to revoke the IP lease, install, then enable TCP/IP.

Also, for sanity check to make sure there are no duplicate DECnet node addresses
on the network.  All you need is for a duplicate running TCP/IP as well.  

(Which is what it looks like by the way).

Jeff