|
Home > Archive > alt.certification.network-plus > January 2003 > HELP! Same IP range, same workgroup, no communication!
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
HELP! Same IP range, same workgroup, no communication!
|
|
| Bill Morris 2003-01-16, 12:24 pm |
| Starting to get desperate: I posted this to two other groups and
haven't had any responses.
In remodeling a room recently, I had to take down the network at home,
shuffle stuff around, then a few days later reconnect everything.
"Everything" consists of a DSL modem, broadband router, and 5 port
switch, plus a Dell laptop (Win2kPro), and 2 generic PCs (Win95 and
Win2KPro, nothing special on either).
* The laptop stayed where it was;
* The Win2K box went to a new "office" (with a new wall plug);
* The Win95 box is waiting for all the remodeling to be finished;
* The modem, router, and switch went to their own spot in the basement
The general configuration is this:
The World
\--> DSL Modem
\--> Broadband Router
\--> Switch
\--> laptop
\--> box
Every device on the network lives somewhere in 192.168.0.*; all ip
addresses are unique; and the laptop and box belong to the "HOMENET"
workgroup. Both computers can use the internet/email/etc. This
configuration is - except for the physical locations of the routers
and box - identical to what I had before (when everything worked), but
the laptop and box cannot browse - or even ping - one another in the
network. All I did was move the equipment, no settings changes or new
software, just moving from a to b. They can communicate with everyone
but each other.
I've tried to think if it's a cabling issue, but if the cables were
connected wrong - or if there were some other hardware problem, I
would think the network would fail completely.
---
Couple of new and hopefully helpful bits of info:
1) The condition described in the message is true whether the
firewalls on each PC are running or not.
2) I switched each PC last night to DHCP using my broadband router as
the DHCP server - before, each PC had an assigned IP. Each PC was
successfully allocated an IP. The problem still exists.
Since there's only one printer and each computer needs access to it,
and I use the network at home to emulate what happens in my office
environment so I can work from home, this is a real show stopper.
I'm at a loss. Anyone have any ideas? Thanks in advance.
Bill Morris
Seritas L.L.C.
| |
| Matt Cavic 2003-01-16, 2:24 pm |
| Hmm. My first guess would be that the route tables on the PC's are
incorrect for some reason. If the PC's were directing all traffic to the
router, even local traffic, then this situation would happen.
Check that the netmask is set to 255.255.255.0 on both PC's, then could
you post a copy of the route table from each PC (route print from a Win
command prompt) along with the IP's of each machine and router?
Matt
N+
On 16 Jan 2003, Bill Morris wrote:
> Starting to get desperate: I posted this to two other groups and
> haven't had any responses.
>
> In remodeling a room recently, I had to take down the network at home,
> shuffle stuff around, then a few days later reconnect everything.
> "Everything" consists of a DSL modem, broadband router, and 5 port
> switch, plus a Dell laptop (Win2kPro), and 2 generic PCs (Win95 and
> Win2KPro, nothing special on either).
>
> * The laptop stayed where it was;
> * The Win2K box went to a new "office" (with a new wall plug);
> * The Win95 box is waiting for all the remodeling to be finished;
> * The modem, router, and switch went to their own spot in the basement
>
> The general configuration is this:
>
> The World
> \--> DSL Modem
> \--> Broadband Router
> \--> Switch
> \--> laptop
> \--> box
>
> Every device on the network lives somewhere in 192.168.0.*; all ip
> addresses are unique; and the laptop and box belong to the "HOMENET"
> workgroup. Both computers can use the internet/email/etc. This
> configuration is - except for the physical locations of the routers
> and box - identical to what I had before (when everything worked), but
> the laptop and box cannot browse - or even ping - one another in the
> network. All I did was move the equipment, no settings changes or new
> software, just moving from a to b. They can communicate with everyone
> but each other.
>
> I've tried to think if it's a cabling issue, but if the cables were
> connected wrong - or if there were some other hardware problem, I
> would think the network would fail completely.
>
> ---
> Couple of new and hopefully helpful bits of info:
>
> 1) The condition described in the message is true whether the
> firewalls on each PC are running or not.
> 2) I switched each PC last night to DHCP using my broadband router as
> the DHCP server - before, each PC had an assigned IP. Each PC was
> successfully allocated an IP. The problem still exists.
>
> Since there's only one printer and each computer needs access to it,
> and I use the network at home to emulate what happens in my office
> environment so I can work from home, this is a real show stopper.
>
> I'm at a loss. Anyone have any ideas? Thanks in advance.
>
> Bill Morris
> Seritas L.L.C.
>
| |
| Steven L Umbach 2003-01-16, 2:24 pm |
| Hi Bill. Did you try pinging other computer by using tcp/ip address instead
of name? Use ipconfig /all at command line on W2K boxes and winipcfg in run
box on W95 boxes to verify tcp/ip configuration on the network adapters.
Make sure all computers are on same network - only the the last .xxx should
be different and of course subnet mask should be 255.255.255.0. If you can
ping each other by tcp/ip address then you have connectivity even if they do
not show up in network neighborhood/places. Assuming you can ping you could
try connecting by using unc -- \\computername\sharename or if that does
not work \\tcp/ip address\sharename . It can take up to something like 46
minutes for computers to show up in network neighborhood/places, so leave
machines on for a while. You may have an issue with browse master election
wars, etc. You can also try net view at the command prompt to view the
browse list and nbtstat -n, nbtstat -c, and nbtstat -r, to see if you are
getting any netbios name resolution at all. W2K machines must also have
netbios over tcp/ip enabled (it is by default) - you can check in tcp/ip
properties/advanced/wins. Since you say all the computers can access the
internet through the same switch, I agree with you that it is not a physical
layer problem and the tcp/ip stack must not be corrupted. Good luck ---
Steve
"Bill Morris" <seamlyne@hotmail.com> wrote in message
news:524123d9.0301160959.1b0338d2@posting.google.com...
> Starting to get desperate: I posted this to two other groups and
> haven't had any responses.
>
> In remodeling a room recently, I had to take down the network at home,
> shuffle stuff around, then a few days later reconnect everything.
> "Everything" consists of a DSL modem, broadband router, and 5 port
> switch, plus a Dell laptop (Win2kPro), and 2 generic PCs (Win95 and
> Win2KPro, nothing special on either).
>
> * The laptop stayed where it was;
> * The Win2K box went to a new "office" (with a new wall plug);
> * The Win95 box is waiting for all the remodeling to be finished;
> * The modem, router, and switch went to their own spot in the basement
>
> The general configuration is this:
>
> The World
> \--> DSL Modem
> \--> Broadband Router
> \--> Switch
> \--> laptop
> \--> box
>
> Every device on the network lives somewhere in 192.168.0.*; all ip
> addresses are unique; and the laptop and box belong to the "HOMENET"
> workgroup. Both computers can use the internet/email/etc. This
> configuration is - except for the physical locations of the routers
> and box - identical to what I had before (when everything worked), but
> the laptop and box cannot browse - or even ping - one another in the
> network. All I did was move the equipment, no settings changes or new
> software, just moving from a to b. They can communicate with everyone
> but each other.
>
> I've tried to think if it's a cabling issue, but if the cables were
> connected wrong - or if there were some other hardware problem, I
> would think the network would fail completely.
>
> ---
> Couple of new and hopefully helpful bits of info:
>
> 1) The condition described in the message is true whether the
> firewalls on each PC are running or not.
> 2) I switched each PC last night to DHCP using my broadband router as
> the DHCP server - before, each PC had an assigned IP. Each PC was
> successfully allocated an IP. The problem still exists.
>
> Since there's only one printer and each computer needs access to it,
> and I use the network at home to emulate what happens in my office
> environment so I can work from home, this is a real show stopper.
>
> I'm at a loss. Anyone have any ideas? Thanks in advance.
>
> Bill Morris
> Seritas L.L.C.
| |
| Bill Morris 2003-01-16, 9:24 pm |
| Wow, thanks for the quick response. So far, only this group has
bothered...it's much appreciated.
Netmask is correct on both machines. Below is the requested
information. Honestly, I'm not sure how to interpret it all, but then
I wouldn't be asking the question, then, would I? 
Matt Cavic <msc141@mscconsult.com> wrote in message news:<Pine.LNX.4.40.0301161326200.16853-100000@linux.michaelsystems.com>...
> Hmm. My first guess would be that the route tables on the PC's are
> incorrect for some reason. If the PC's were directing all traffic to the
> router, even local traffic, then this situation would happen.
>
> Check that the netmask is set to 255.255.255.0 on both PC's, then could
> you post a copy of the route table from each PC (route print from a Win
> command prompt) along with the IP's of each machine and router?
>
> Matt
> N+
>
For the Win2K box:
==============================
==============================
===============
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 50 04 ae 1a d8 ...... 3Com EtherLink PCI
==============================
==============================
===============
==============================
==============================
===============
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.20
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.20 192.168.0.20
1
192.168.0.20 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.0.255 255.255.255.255 192.168.0.20 192.168.0.20
1
224.0.0.0 224.0.0.0 192.168.0.20 192.168.0.20
1
255.255.255.255 255.255.255.255 192.168.0.20 192.168.0.20
1
Default Gateway: 192.168.0.1
==============================
==============================
===============
Persistent Routes:
None
C:\>ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : swbell.net
IP Address. . . . . . . . . . . . : 192.168.0.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
For the laptop (also Win2K)
C:\>route print
==============================
==============================
===============
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 20 e0 68 0a c6 ...... Intel 8255x-based Integrated
Fast Ethernet
==============================
==============================
===============
==============================
==============================
===============
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.22
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.22 192.168.0.22
1
192.168.0.22 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.0.255 255.255.255.255 192.168.0.22 192.168.0.22
1
224.0.0.0 224.0.0.0 192.168.0.22 192.168.0.22
1
255.255.255.255 255.255.255.255 192.168.0.22 192.168.0.22
1
Default Gateway: 192.168.0.1
==============================
==============================
===============
Persistent Routes:
None
C:\>ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : swbell.net
IP Address. . . . . . . . . . . . : 192.168.0.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
The Windows 95 machine is still unconnected.
| |
| Bill Morris 2003-01-16, 9:24 pm |
| "Steven L Umbach" <sumbach@ameritech.net> wrote in message news:<7JEV9.95$4y6.60771@newssrv26.news.prodigy.com>...
> Hi Bill. Did you try pinging other computer by using tcp/ip address instead
> of name?
Ping either way fails.
> Make sure all computers are on same network - only the the last .xxx should
> be different and of course subnet mask should be 255.255.255.0.
All correct.
> ping each other by tcp/ip address then you have connectivity even if they do
> not show up in network neighborhood/places. Assuming you can ping you could
> try connecting by using unc -- \\computername\sharename or if that does
> not work \\tcp/ip address\sharename . It can take up to something like 46
> minutes for computers to show up in network neighborhood/places, so leave
> machines on for a while.
The machines are never shut off. Network Neighborhood is usually the
last place I look, because of that lag - I always ping first, because
it's more reliable.
You may have an issue with browse master election
> wars, etc. You can also try net view at the command prompt to view the
> browse list and nbtstat -n, nbtstat -c, and nbtstat -r, to see if you are
> getting any netbios name resolution at all.
Only to the name of the local machine.
> netbios over tcp/ip enabled (it is by default) - you can check in tcp/ip
> properties/advanced/wins.
And so it is.
> Since you say all the computers can access the
> internet through the same switch, I agree with you that it is not a physical
> layer problem and the tcp/ip stack must not be corrupted.
The company I bought the switch from said much the same thing - at
least about their product. Still searching...
- Bill
| |
| Steven L Umbach 2003-01-16, 11:24 pm |
| Hmm. Interesting. I would leave any firewalls on the computers disabled
until you get everything working. Try shutting off power to the switch,
change the ports that the computers are plugged into and power the switch
back up. Some switches can not use port 1 if the uplink port is being
used - double check switch settings (maybe a push button) and that nothing
there has changed such as configuration for fixed speed or auto sense. If
nothing else helps try to connect the two computers together with a
crossover cable to see if they can communicate with each other assumming
nics are same speed. You would want to configure them with static addresses
if you do that though. Also try to get another computer on the network to
see what happens. --- Steve
"Bill Morris" <seamlyne@hotmail.com> wrote in message
news:524123d9.0301161837.72569b0c@posting.google.com...
> "Steven L Umbach" <sumbach@ameritech.net> wrote in message
news:<7JEV9.95$4y6.60771@newssrv26.news.prodigy.com>...
> > Hi Bill. Did you try pinging other computer by using tcp/ip address
instead
> > of name?
>
> Ping either way fails.
>
> > Make sure all computers are on same network - only the the last .xxx
should
> > be different and of course subnet mask should be 255.255.255.0.
>
> All correct.
>
> > ping each other by tcp/ip address then you have connectivity even if
they do
> > not show up in network neighborhood/places. Assuming you can ping you
could
> > try connecting by using unc -- \\computername\sharename or if that
does
> > not work \\tcp/ip address\sharename . It can take up to something like
46
> > minutes for computers to show up in network neighborhood/places, so
leave
> > machines on for a while.
>
> The machines are never shut off. Network Neighborhood is usually the
> last place I look, because of that lag - I always ping first, because
> it's more reliable.
>
>
> You may have an issue with browse master election
> > wars, etc. You can also try net view at the command prompt to view the
> > browse list and nbtstat -n, nbtstat -c, and nbtstat -r, to see if you
are
> > getting any netbios name resolution at all.
>
> Only to the name of the local machine.
>
> > netbios over tcp/ip enabled (it is by default) - you can check in tcp/ip
> > properties/advanced/wins.
>
> And so it is.
>
> > Since you say all the computers can access the
> > internet through the same switch, I agree with you that it is not a
physical
> > layer problem and the tcp/ip stack must not be corrupted.
>
> The company I bought the switch from said much the same thing - at
> least about their product. Still searching...
>
> - Bill
| |
| Bill Morris 2003-01-17, 7:24 pm |
| Steven, you just provided the clue that got me where I need to be!
In my case, the uplink port and port 5 are the problems: without
knowing, I'd wired the wall socket to work only with port 5 - the
(terminology?) crossover port. What I didn't figure on was that in
that configuration, port 5 wouldn't be able to communicate with ports
1-4. Once I rewired the wall socket and used port N, where N is any
number between 1 and 4 but NOT 5, everything came back.
Thanks to everyone who donated a brain cell or two!!
- Bill
"Steven L Umbach" <n9rou@attbi.com> wrote in message news:<jGLV9.17138$1q3.2037@sccrnsc01>...
> Hmm. Interesting. I would leave any firewalls on the computers disabled
> until you get everything working. Try shutting off power to the switch,
> change the ports that the computers are plugged into and power the switch
> back up. Some switches can not use port 1 if the uplink port is being
> used - double check switch settings (maybe a push button) and that nothing
> there has changed such as configuration for fixed speed or auto sense. If
> nothing else helps try to connect the two computers together with a
> crossover cable to see if they can communicate with each other assumming
> nics are same speed. You would want to configure them with static addresses
> if you do that though. Also try to get another computer on the network to
> see what happens. --- Steve
>
| |
| Steven L Umbach 2003-01-18, 11:24 am |
| Excellent Bill. Glad you got it working. --- Steve
"Bill Morris" <wmorris@seamlyne.com> wrote in message
news:432d6672.0301171634.476f750d@posting.google.com...
> Steven, you just provided the clue that got me where I need to be!
>
> In my case, the uplink port and port 5 are the problems: without
> knowing, I'd wired the wall socket to work only with port 5 - the
> (terminology?) crossover port. What I didn't figure on was that in
> that configuration, port 5 wouldn't be able to communicate with ports
> 1-4. Once I rewired the wall socket and used port N, where N is any
> number between 1 and 4 but NOT 5, everything came back.
>
> Thanks to everyone who donated a brain cell or two!!
>
> - Bill
>
> "Steven L Umbach" <n9rou@attbi.com> wrote in message
news:<jGLV9.17138$1q3.2037@sccrnsc01>...
> > Hmm. Interesting. I would leave any firewalls on the computers disabled
> > until you get everything working. Try shutting off power to the switch,
> > change the ports that the computers are plugged into and power the
switch
> > back up. Some switches can not use port 1 if the uplink port is being
> > used - double check switch settings (maybe a push button) and that
nothing
> > there has changed such as configuration for fixed speed or auto sense.
If
> > nothing else helps try to connect the two computers together with a
> > crossover cable to see if they can communicate with each other assumming
> > nics are same speed. You would want to configure them with static
addresses
> > if you do that though. Also try to get another computer on the network
to
> > see what happens. --- Steve
> >
|
|
|
|
|