|
Zule (m)
|
i have a problem with my network
really serious problem
i am having a LAN problem in my office
my work system browse for some few minutes and in the next mintues displays
"the page can not be display"
i am sure this problem is not from my ISP i have comfirmed from them
when
i am operating on a v-sat
when i ping my router
it reply and times out at interval in the form shown below
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time =4ms TTL=64
reply from 192.168.***.***: byte=32 time =9ms TTL=64
reply from 192.168.***.***: byte=32 time =20ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time =4ms TTL=64
reply from 192.168.***.***: byte=32 time =9ms TTL=64
reply from 192.168.***.***: byte=32 time =20ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
and so on
this problem is the in all systems
initial i thought it was a virus problem because before the above problem appeared the whole clientS including the server was flashing a message IP CONLICT BUT I WAS SURE I WASN'T HAVING A CONFLICT IN MY NAMING.
so i tried formated the whole system sever inclusive still did not solve the problem
finally i decided to change my server operating system to MIKROTIK ROUTER OS
I WAS ABLE to stop the IP CONLICT
how ever i am still having this problem
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time =4ms TTL=64
reply from 192.168.***.***: byte=32 time =9ms TTL=64
reply from 192.168.***.***: byte=32 time =20ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time <1ms TTL=64
reply from 192.168.***.***: byte=32 time =4ms TTL=64
reply from 192.168.***.***: byte=32 time =9ms TTL=64
reply from 192.168.***.***: byte=32 time =20ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
|
|
|
|
|
|
Zule (m)
|
I AM PLANING TO DO A FRESH NETWORKING RENTWORK ALL THE CAT5 IN FACT START RENETWORKING
ADVISE NEEDED please
|
|
|
|
|
|
Maleeq (m)
|
Do you get a continuous reply when you ping other systems and not the router?
If you do, then the problem points more to the router than the entire network.
Check:
- Confirm the router is ok. I have never used a Mikrokir router and so I would not be able to give procedure(s) in doing this.
- If the router is ok, confirm the cabling to the router
- Check your switch.
This problem can't be from the systems. So, you need not format them or re-cable your entire network
As for the IP conflict issues, do you have a DHCP server on the network?(or does the router servers this purpose?). Before DHCP servers issue an IP, it checks for its availability on the network. You could get IP conflict messages during this checks - This is an indication that your scope needs reconciliation.
|
|
|
|
|
|
Zule (m)
|
Do you get a continuous reply when you ping other systems and not the router?
If you do, then the problem points more to the router than the entire network.
Check:
- Confirm the router is ok. I have never used a Mikrokir router and so I would not be able to give procedure(s) in doing this.
- If the router is ok, confirm the cabling to the router
- Check your switch.
This problem can't be from the systems. So, you need not format them or re-cable your entire network
As for the IP conflict issues, do you have a DHCP server on the network?(or does the router servers this purpose?). Before DHCP servers issue an IP, it checks for its availability on the network. You could get IP conflict messages during this checks - This is an indication that your scope needs reconciliation.
i have no problem with conflict any more as for the systems they reply very well to and fro ine another now what i did is this i have transfer the cat5 cables to a second HUB and left some few with the exsiting hub at lest for now the reply is now this Reply from 192.168.0.1: bytes=32 time <1ms TTL=64 Reply from 192.168.0.1: bytes=32 time <1ms TTL=64 Reply from 192.168.0.1: bytes=32 time <1ms TTL=64 Reply from 192.168.0.1: bytes=32 time =32ms TTL=64 Reply from 192.168.0.1: bytes=32 time =9ms TTL=64 Reply from 192.168.0.1: bytes=32 time =23msTTL=64 Reply from 192.168.0.1: bytes=32 time <1ms TTL=64 Reply from 192.168.0.1: bytes=32 time <1ms TTL=64 |
|
|
|
|
|
Zule (m)
|
still on it no time out for now
|
|
|
|
|
|
Zule (m)
|
but do u think some ports in the old HUb is faulty
or what
could that be over load? or what
|
|
|
|
|
|
Maleeq (m)
|
You use a hub? You know that hubs create a flat network with one broadcast domain, no media contention detection nor correction?
It sounds thats the problem. It could have faulty ports. Another reason could be a system on your network is broadcasting excessively, this is a possible cause.
You should try using a switch instead of a hub for your network.
|
|
|
|
|
|
Ralvy (m)
|
Please be more elaborate, it depends on the kind of connection u used, I hope u r nt using the mesh topology which makes all the systems have the same status, such networks are very difficult to trouble shoot,
I am guessing u are using a small area network just to connect networking devices,
I also hope u have not crossed boundaries, the type of cable u are using matters,
If it is the thinnet (10base2), the Layin shuld nt be more than 100metres or there about, u shuld do this only if u are using the thicknet (10base5) coaxial cables or u will realise allenuation (signal loss),
Repost the subject elaborating every single thing, the kind of cables used and also let us know if a single cable is run through out the network as a backbone and also how the computers are linked up,
Please answer these questions when replying;
1. Is Printer and File Sharing still active?
2. Does the Server connect to the Internet?
3. How long is the cabling?
I am looking forward tu ur post 
|
|
|
|
|
|
Zule (m)
|
Please be more elaborate, it depends on the kind of connection u used, I hope you're nt using the mesh topology which makes all the systems have the same status, such networks are very difficult to trouble shoot,
I am guessing u are using a small area network just to connect networking devices,
I also hope u have not crossed boundaries, the type of cable u are using matters,
If it is the thinnet (10base2), the Layin shuld nt be more than 100metres or there about, u shuld do this only if u are using the thicknet (10base5) coaxial cables or u will realise allenuation (signal loss),
Repost the subject elaborating every single thing, the kind of cables used and also let us know if a single cable is run through out the network as a backbone and also how the computers are linked up,
Please answer these questions when replying;
1. Is Printer and File Sharing still active?
2. Does the Server connect to the Internet?
3. How long is the cabling?
I am looking forward tu your post file and printer sharing is not active on my server i am using router operating system on my server when i ping the my ISP it replies my cabling is ok i am using star topolgy |
|
|
|
|
|
Zule (m)
|
SINCE 4:00AM TILL NOW THE NETWORK IS STILL IN GOOD CONDITION
REPLIES ARE OK
BUT THEN AM NOT CONCLUDING YET
|
|
|
|
|
|
Zule (m)
|
You use a hub? You know that hubs create a flat network with one broadcast domain, no media contention detection nor correction?
It sounds thats the problem. It could have faulty ports. Another reason could be a system on your network is broadcasting excessively, this is a possible cause.
You should try using a switch instead of a hub for your network.
What do u mean by Another reason could be a system on your network is broadcasting excessivelybut if that is the case what will happen |
|
|
|
|
|
Zule (m)
|
hello, i observed something i have a system that when my server from i get something like this
Reply from 192.168.0.1: bytes=32 time <1ms TTL=64
Reply from 192.168.0.1: bytes=32 time <1ms TTL=64
Reply from 192.168.0.1: bytes=32 time <32ms TTL=64
Reply from 192.168.0.1: bytes=32 time =32ms TTL=64
Reply from 192.168.0.1: bytes=32 time =9ms TTL=64
Reply from 192.168.0.1: bytes=32 time =23msTTL=64
Reply from 192.168.0.1: bytes=32 time <24ms TTL=64
Reply from 192.168.0.1: bytes=32 time <45ms TTL=64
Reply from 192.168.0.1: bytes=32 time <1ms TTL=64
Reply from 192.168.0.1: bytes=32 time <1ms TTL=64
Reply from 192.168.0.1: bytes=32 time <32ms TTL=64
Reply from 192.168.0.1: bytes=32 time =32ms TTL=64
Reply from 192.168.0.1: bytes=32 time =9ms TTL=64
Reply from 192.168.0.1: bytes=32 time =23msTTL=64
Reply from 192.168.0.1: bytes=32 time <24ms TTL=64
Reply from 192.168.0.1: bytes=32 time <45ms TTL=64
check the ms side
is this normal
|
|
|
|
|
|
Zule (m)
|
@Maleeq
it this what u mean by working excessively
|
|
|
|
|
|
Maleeq (m)
|
In a network, systems send broadcast messages(service discovery, pnp device discovery, network awareness, ARP request and so on, ). This messages are received by all the systems on the network segment where the it originates, and they most all process the information.
OR
this can occur when you have a faulty NIC (Network Interface Card) on one of the systems or a malware is on a system that is possibly trying to utilize the connection to send information through the internet or simply "clogging" your network. These are all possibilities.
Now, you mentioned using a hub, when there's a broadcast on the network, all other hosts on the segment stop to process that message, and possibly, reply depending on the message type. No thanks to the hub, collisions must occur, and they keep re-transmitting over and over. If at this point your try pinging any system, you'll get unreasonable echo reply times.
If the number of systems you have on your network is too much, try checking the "Network utilization" statistics under "Task Manager", and select the "Nonunicast Received/Interval" display option. If the value is high, then you know that is the system responsible for the network clogging.
|
|
|
|
|
|
![Nairaland [Nigerian Forum] Home](http://www.nairaland.com/Themes/default/images/english/home.gif)
Author
