HomeBrew
11-03-2002, 10:24 AM
I have just finished setting up a Linux box (Red Hat 8.0) to my home network (I'm a newbie, but learning fast). The network comprises 6 Windows machines (4 XP Home, and 2 Win98SE) and the Linux box, linked through a D-Link router. All is working fine. Then why am I posting?
Well, there's this wierd problem-that-is-not-a-problem-but-is-bugging-me. When I issue the nmblookup command, I get results from six computers, but one is missing (192.168.0.123, a WinXP machine). All of the WinXP machines are configured identically, at least as far as I can tell (same network services, protocols, and clients installed).
The server (192.168.0.110) and the missing WinXP machine can talk to one another (I have shares setup via Samba, and it works fine). The machine that's missing is also a dual boot machine, and when running as a RH 8.0 client, it can also mount NFS shares from the server. In fact, you can see that I ran the command (results below) from 192,168.0.123, though the results are the same if run from the terminal of the server:
Last login: Sun Nov 3 07:54:50 2002 from 192.168.0.123
[root@Helix root]# nmblookup -d 2 "*"
added interface ip=192.168.0.110 bcast=192.168.0.255 nmask=255.255.255.0
querying * on 192.168.0.255
Got a positive name query response from 192.168.0.110 ( 192.168.0.110 )
Got a positive name query response from 192.168.0.153 ( 192.168.0.153 )
Got a positive name query response from 192.168.0.122 ( 192.168.0.122 )
Got a positive name query response from 192.168.0.181 ( 192.168.0.181 )
Got a positive name query response from 192.168.0.177 ( 192.168.0.177 )
Got a positive name query response from 192.168.0.107 ( 192.168.0.107 )
192.168.0.110 *<00>
192.168.0.153 *<00>
192.168.0.122 *<00>
192.168.0.181 *<00>
192.168.0.177 *<00>
192.168.0.107 *<00>
[root@Helix root]#
As I said, this seems to be an "invisible" problem, as everything is working. But, there is some reason why this one machine is behaving differently from the others, and I'm afraid that if left this way, it might come back and bite me later.
Any idea what might be causing this?
Well, there's this wierd problem-that-is-not-a-problem-but-is-bugging-me. When I issue the nmblookup command, I get results from six computers, but one is missing (192.168.0.123, a WinXP machine). All of the WinXP machines are configured identically, at least as far as I can tell (same network services, protocols, and clients installed).
The server (192.168.0.110) and the missing WinXP machine can talk to one another (I have shares setup via Samba, and it works fine). The machine that's missing is also a dual boot machine, and when running as a RH 8.0 client, it can also mount NFS shares from the server. In fact, you can see that I ran the command (results below) from 192,168.0.123, though the results are the same if run from the terminal of the server:
Last login: Sun Nov 3 07:54:50 2002 from 192.168.0.123
[root@Helix root]# nmblookup -d 2 "*"
added interface ip=192.168.0.110 bcast=192.168.0.255 nmask=255.255.255.0
querying * on 192.168.0.255
Got a positive name query response from 192.168.0.110 ( 192.168.0.110 )
Got a positive name query response from 192.168.0.153 ( 192.168.0.153 )
Got a positive name query response from 192.168.0.122 ( 192.168.0.122 )
Got a positive name query response from 192.168.0.181 ( 192.168.0.181 )
Got a positive name query response from 192.168.0.177 ( 192.168.0.177 )
Got a positive name query response from 192.168.0.107 ( 192.168.0.107 )
192.168.0.110 *<00>
192.168.0.153 *<00>
192.168.0.122 *<00>
192.168.0.181 *<00>
192.168.0.177 *<00>
192.168.0.107 *<00>
[root@Helix root]#
As I said, this seems to be an "invisible" problem, as everything is working. But, there is some reason why this one machine is behaving differently from the others, and I'm afraid that if left this way, it might come back and bite me later.
Any idea what might be causing this?