2006-09-30 hypertwins network issues - Revision history

Woozle: /* Solution */ another glitch

2006-09-30T17:40:09Z

Solution: another glitch

← Older revision		Revision as of 17:40, 30 September 2006
Line 34:		Line 34:
	Name: gonzo		Name: gonzo
	Address: 192.168.0.254		Address: 192.168.0.254
			==Another Glitch==
			For some reason, Gonzo stopped responding to [[nmblookup]], i.e. other machines couldn't see him, even though they could still ping him by name. It turned out that Gonzo's [[nmbd]] somehow got started under my regular-user account instead of by root; killing that process and then restarting Samba (as root; /etc/init.d/samba restart) fixed the problem.

Woozle: /* Overview */ I think I must have meant nmblookup; no such thing as smblookup

2006-09-30T17:16:27Z

Overview: I think I must have meant nmblookup; no such thing as smblookup

← Older revision		Revision as of 17:16, 30 September 2006
Line 1:		Line 1:
	==Overview==		==Overview==
	[[category:hypertwins network]][[category:dated items]]Latest network issues from {{thehypertwins}}:		[[category:hypertwins network]][[category:dated items]]Latest network issues from {{thehypertwins}}:
	* Bunsen resolves correct IP address for Gonzo via ping, [[~~smblookup~~]], and net lookup, but browsing smb://gonzo shows bunsen's shares instead.		* Bunsen resolves correct IP address for Gonzo via ping, [[nmblookup]], and net lookup, but browsing smb://gonzo shows bunsen's shares instead.
	*: This is after a complete shutdown/restart, after which I found that the lisa daemon wasn't running, and had to start it by hand.		*: This is after a complete shutdown/restart, after which I found that the lisa daemon wasn't running, and had to start it by hand.
	*: I couldn't figure out why lisa didn't run automatically because the Red Hat services GUI app wouldn't run. I don't know how else to check what things are supposed to run automatically at bootup.		*: I couldn't figure out why lisa didn't run automatically because the Red Hat services GUI app wouldn't run. I don't know how else to check what things are supposed to run automatically at bootup.
Line 9:		Line 9:

	There was one glitch I fixed earlier, which was that gonzo had an entry in [[/etc/hosts]] to return 128.0.1.1 for "gonzo". After I fixed that, Bunsen started working again, but only for a little bit.		There was one glitch I fixed earlier, which was that gonzo had an entry in [[/etc/hosts]] to return 128.0.1.1 for "gonzo". After I fixed that, Bunsen started working again, but only for a little bit.

	==Part 2==		==Part 2==
	[woozle@Bunsen ~]$ nslookup gonzo		[woozle@Bunsen ~]$ nslookup gonzo

Woozle: fixed it

2006-09-30T14:32:43Z

fixed it

@@ Line 1: / Line 1: @@
 [[category:hypertwins network]][[category:dated items]]Latest network issues from {{thehypertwins}}:
 * Bunsen resolves correct IP address for Gonzo via ping, [[smblookup]], and net lookup, but browsing smb://gonzo shows bunsen's shares instead.
@@ Line 8: / Line 9: @@
 There was one glitch I fixed earlier, which was that gonzo had an entry in [[/etc/hosts]] to return 128.0.1.1 for "gonzo". After I fixed that, Bunsen started working again, but only for a little bit.

Woozle: category: hypertwins +network

2006-09-30T13:09:02Z

category: hypertwins +network

← Older revision		Revision as of 13:09, 30 September 2006
Line 1:		Line 1:
	[[category:hypertwins]][[category:dated items]]Latest network issues from {{thehypertwins}}:		[[category:hypertwins network]][[category:dated items]]Latest network issues from {{thehypertwins}}:
	* Bunsen resolves correct IP address for Gonzo via ping, [[smblookup]], and net lookup, but browsing smb://gonzo shows bunsen's shares instead.		* Bunsen resolves correct IP address for Gonzo via ping, [[smblookup]], and net lookup, but browsing smb://gonzo shows bunsen's shares instead.
	*: This is after a complete shutdown/restart, after which I found that the lisa daemon wasn't running, and had to start it by hand.		*: This is after a complete shutdown/restart, after which I found that the lisa daemon wasn't running, and had to start it by hand.

Woozle at 13:08, 30 September 2006

2006-09-30T13:08:06Z

New page

[[category:hypertwins]][[category:dated items]]Latest network issues from {{thehypertwins}}:
* Bunsen resolves correct IP address for Gonzo via ping, [[smblookup]], and net lookup, but browsing smb://gonzo shows bunsen's shares instead.
*: This is after a complete shutdown/restart, after which I found that the lisa daemon wasn't running, and had to start it by hand.
*: I couldn't figure out why lisa didn't run automatically because the Red Hat services GUI app wouldn't run. I don't know how else to check what things are supposed to run automatically at bootup.
*: Also... [[smbtree]] on Bunsen showed the correct shares for Gonzo. So it's not Samba, but somewhere between Konqueror and Samba.
* Floyd shows everything messed-up, but can't reboot Floyd at the moment because he's running things which need to stay connected.
* Looking at the network from two other machines (one [[win98]] and one [[Ubuntu]]), everything looks as it should.

There was one glitch I fixed earlier, which was that gonzo had an entry in [[/etc/hosts]] to return 128.0.1.1 for "gonzo". After I fixed that, Bunsen started working again, but only for a little bit.