Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: networking trouble
- To: tlug@example.com
- Subject: Re: networking trouble
- From: Jonathan Q <jq@example.com>
- Date: Fri, 25 May 2001 14:43:14 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <3B0DEE65.3B255773@example.com>; from 9915104t@example.com on Fri, May 25, 2001 at 02:32:21PM +0900
- References: <3B0DEE65.3B255773@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <TwkPnB.A.qZE.jFfD7@example.com>
- Resent-Sender: tlug-request@example.com
If your IPs and netmasks are really set up as below, that's probably your problem: you're trying to gene-splice apples and oranges here :-) B0Ti (9915104t@example.com) wrote: > IP address: 192.168.1.83 (assigned by the ISP) > Netmask: 255.255.0.0 > Gateway: 192.168.1.254 Try 255.255.255.0 netmask. 192.168.1.0 is non-routable class C network. > IP address: 192.168.2.10 > Netmask: 255.255.0.0 > Gateway: 192.168.1.83 192.168.2.0 is also a non-routable class C. Try renumbering this to 192.168.1.10 and see if it helps. Mask 255.255.255.0 > vmware: > IP address: 192.168.2.11 > Netmask: 255.255.0.0 > Gateway: 192.168.1.83 Like above, renumber this to 192.168.1.11 255.255.255.0. That should make everything work. Jonathan
- Follow-Ups:
- Re: networking trouble
- From: B0Ti <9915104t@example.com>
- References:
- networking trouble
- From: B0Ti <9915104t@example.com>
Home | Main Index | Thread Index
- Prev by Date: networking trouble
- Next by Date: Re: networking trouble
- Prev by thread: networking trouble
- Next by thread: Re: networking trouble
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links