Re: Perils of Gwendolyn (er, 8364 futzing)

Hi Louis,

Yes, I'm still alive, albeit barely... after a very stressful year and
moving to our new house, my body sorta broke down.
What started out as a mild cold, ended with a serious bout of the flu. Fever
running high at 103 F / 39.5 C. Really enjoyed that ;-).
After almost a week, the temp is still not back to normal. And my lungs
still have a tendency to have a look at life on the outside, if you catch my
drift.

But hey, that's nothing compared to your problems, is it?

"Louis Ohland" <ohland@xxxxxxxxxxx> schreef in bericht
news:IKzMh.23$nT3.14@xxxxxxxxxxxxxxx
Kevin, what we have here is failure to communicate.

This machine works (typing on it now)
Windows 98 IP Configuration [for 760XL]
Host Name . . . . . . . . . : 760XL.mad.wi.charter.com

This one doesn't
Windows 98 IP Configuration [for 8364]
Host Name . . . . . . . . . : NETVISTA

BOTH are plugged into the same wireless router. If I ran ipconfig on my NT
box downstairs it most likely would report 9595.mad.wi.charter.com as
well.

The Netvista has a valid DHCP lease from the downstairs router. It has an
assigned address, set by the downstairs router. But it won't talk to it
via PING or HTTPS.

I love ASCII art...

Oh, yes!

8364 (Netvista)
Downstairs Upstairs --->192.168.1.128
WHR-G54S WHR-G54S | LAN Port
ISP --> 192.168.1.1 (((((((((( 192.168.1.2 ----|
DHCP Server DHCP Disabled | 760XL (760XL)
--->192.168.1.105
LAN Port

The beauty of it all....


NOTE: "((((" stands for wireless link.
"----" stands for CAT5 cable
Using DD-WRT, v23 SP2

http://www.gilanet.com/ohlandl/NIC/whr-g54s.html#Client_Bridge

Kevin Bowling wrote:
Louis Ohland wrote:
Kevin, I did a shutdown then a power off. Gateway is still 192.168.1.1

Both systems are the same (except the 8364 uses an Intel PRO/100+
Management Adapter). The difference is that the 8364 says the Host Name
is "NETVISTA", while the 760XL reports machine/ISP.

Hostname shouldn't matter, that could only affect name resolution like
'ping 760XL'. Intel PRO+ are very good (remember: I use these machines
as routers), in fact all Intel networking gear is top notch. If the
network is setup to do transparent bridging, every thing looks a go to
me. One way to rule out some possibilities would be to eliminate the
bridge, by hooking the machine up to the WAN router.

This is from the 760XL, which does get through to the downstairs router,
and then to the internet:
Windows 98 IP Configuration [for 760XL]
Host Name . . . . . . . . . : 760XL.mad.wi.charter.com
DNS Servers . . . . . . . . : 192.168.1.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :
Description . . . . . . . . : Belkin F5D5020 PCMCIA Card Network Card.
Physical Address. . . . . . : 00-XX-XX-XX-5F-F3
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.105
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 03 22 07 08:19:49
Lease Expires . . . . . . . : 03 23 07 08:19:49


This is from the confused system:
Windows 98 IP Configuration [for 8364]
Host Name . . . . . . . . . : NETVISTA
DNS Servers . . . . . . . . : 192.168.1.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :
Description . . . . . . . . : Intel PRO/100+ Management Adapter
Physical Address. . . . . . : 00-XX-XX-XX-8B-3A
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.128
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 03 22 07 08:39:52
Lease Expires . . . . . . . : 03 23 07 08:39:52

The Intel PRO 100 was discussed earlier in this thread
http://tinylink.com/?mD4cwfZPMy (you asked William, but I didn't see a reply
yet).

OTOH it could be that you have an issue with the (use of the) HOSTS-file. As
is stated in http://support.microsoft.com/?kbid=105997 :
"In Windows NT, the HOSTS file is for TCP/IP utilities, and the LMHOSTS file
is for LAN Manager NET utilities. If you cannot PING another computer (using
a friendly name), check the HOSTS file. If you cannot NET VIEW a server
using only the TCP/IP protocol, check the LMHOSTS file."

Now I know that this article relates to NT, but I also know that using the
HOSTS-files with W95/W98 did resolve several issues concerning networking.
Couldn't hurt to try, could it?
Why it would be necessary on the Netvista and not on the 760XL?? Beats me...
could be a slight difference in the W98 installation between the two.

For additional reading :
http://msdn2.microsoft.com/en-us/library/ms810277.aspx

LMHOSTS
* Appendix G - HOSTS and LMHOSTS Files for Windows 95, from Windows 95
Resource Kits.
* Appendix F - HOSTS and LMHOSTS Files for Windows 98, from Windows 98
Resource Kits.
* Chapter 33 - Using LMHOSTS Files, from Windows NT Workstation 4.0
Resource Kits.
* Chapter 10 - Using LMHOSTS Files, from Windows NT Server 4.0 Resource
Kits.
* Appendix H - LMHOSTS File, from Windows 2000 Server Resource Kits.
* KB101927 - The Lmhosts File for TCP/IP in Windows
* KB102725 - LMHOSTS File Information and Predefined Keywords
* KB314884 - LMHOSTS File Information and Predefined Keywords
* KB110976 - LMHOSTS Keywords Must Be Uppercase
* KB262655 - Primary Domain Controller (PDC) Names Entered in LMHOSTS
File Are Case-Sensitive
* KB150800 - Domain Browsing with TCP/IP and LMHOSTS Files
* KB180099 - Troubleshooting LMHOSTS Name Resolution Issues
* KB180094 - How to Write an LMHOSTS File for Domain Validation and
Other Name Resolution Issues
* KB314108 - How to Write an LMHOSTS File for Domain Validation and
Other Name Resolution Issues

HTTH

--
Jelte
The information contained in this post is copyright the poster
and specifically may not be published in, or used by
http://www.jlaforums.com



.

Relevant Pages

  • Re: Moving FSMO roles to a new DC
    ... the name resolution method I used is lmhosts file. ... easy to change the IP address of the PDCe and PDC on lmhosts file. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Perils of Gwendolyn (er, 8364 futzing)
    ... The Netvista has a valid DHCP lease from the downstairs router. ... Windows 98 IP Configuration ... NetBIOS Resolution Uses DNS: No ... Appendix H - LMHOSTS File, from Windows 2000 Server Resource Kits. ...
    (comp.sys.ibm.ps2.hardware)
  • Re: Perils of Gwendolyn (er, 8364 futzing)
    ... Shouldn't DHCP remove the need for a HOSTS or LMHOSTS? ... Windows 98 IP Configuration ... NetBIOS Resolution Uses DNS: No ... Appendix H - LMHOSTS File, from Windows 2000 Server Resource Kits. ...
    (comp.sys.ibm.ps2.hardware)
  • Re: Samba Resolution Problem: named.conf?
    ... Add and entry to the lmhosts file on the windows box. ... > might configure named.conf for correct name resolution? ...
    (alt.os.linux)
  • Re: Network host insists on retaining wrong ip address for client
    ... Host can ping the laptop by ip address, ... the host computer's lmhosts file the laptop's address is correct. ... Is Windows Firewall the only security program involved here? ... There is a section on name resolution under NBT, ...
    (microsoft.public.windowsxp.network_web)