problem in LAN

  • Thread starter Thread starter Robert
  • Start date Start date
R

Robert

The problem is 2 of the systems in lan can't be accessed by
any other system in the LAN where as these 2 system can access any
other system on the LAN.Only possible way for other system to connect
to the faulty system is after these system has established a
connection with the system trying to it.
Click to expand...

When you say 'can not be accessed' are you talking by name or by ip
address?

Also these 2 machine are they Linux or Windows machines? and what are the
other desktop machine?


--

Regards
Robert

Smile... it increases your face value!
 
Hi All !
I have a very strange problem !!Begining with my n/w
architecture i have servers on linux (DNS,mail & gateway ) connected
to them is 50 work stations we donot have a domain we have a common
workgroup across the network,each computer is give a static ip between
192.168.0.10 to 192.168.0.255 with subnet as 244.255.255.0.
192.168.0.1 and 192.168.0.2 are our dns servers and 192.168.0.9 is
the gateway !
The problem is 2 of the systems in lan can't be accessed by
any other system in the LAN where as these 2 system can access any
other system on the LAN.Only possible way for other system to connect
to the faulty system is after these system has established a
connection with the system trying to it.


REgards,
Guru
 
Hi All !
I have a very strange problem !!Begining with my n/w
architecture i have servers on linux (DNS,mail & gateway ) connected
to them is 50 work stations we donot have a domain we have a common
workgroup across the network,each computer is give a static ip between
192.168.0.10 to 192.168.0.255
Click to expand...

I thought x.x.x.255 was a broadcast number, if so, hope it is not
given to a computer.
with subnet as 244.255.255.0.
192.168.0.1 and 192.168.0.2 are our dns servers and 192.168.0.9 is
the gateway !
The problem is 2 of the systems in lan can't be accessed by
any other system in the LAN where as these 2 system can access any
other system on the LAN.Only possible way for other system to connect
to the faulty system is after these system has established a
connection with the system trying to it.
Click to expand...

I would
verify /etc/hosts matches ip address on those two systems
verify /etc/hosts does not have duplicate ip addresse
and if correct, I would swap out the nic to make sure it's mac address
is not the problem.
 
james!
That was a typing mistake te subnet is 255.255.255.0! itz
windows machine .Access by either the system name or by ip results in
the same!i changed the nic but no help...I could temporarily fix the
problem by uninstalling the tcp/ip protocol and other protocols in the
the LAN properties but when the system is rebooted the problem
returns!!

Regards,
guru
:-(
 
james!
That was a typing mistake te subnet is 255.255.255.0! itz
windows machine .Access by either the system name or by ip results in
the same!i changed the nic but no help...I could temporarily fix the
problem by uninstalling the tcp/ip protocol and other protocols in the
the LAN properties but when the system is rebooted the problem
returns!!

Regards,
guru
:-(
 
Robert!
That was a typing mistake te subnet is 255.255.255.0! itz
windows machine .Access by either the system name or by ip results in
the same!i changed the nic but no help...I could temporarily fix the
problem by uninstalling the tcp/ip protocol and other protocols in the
the LAN properties but when the system is rebooted the problem
returns!!

Regards,
guru
:-(
 
Hi Guru,
Access by either the system name or by ip results in
the same!i changed the nic but no help...I could temporarily fix the
problem by uninstalling the tcp/ip protocol and other protocols in the
the LAN properties but when the system is rebooted the problem
returns!!
Click to expand...

I have seen something like this some time ago when the TCP/IP 16 bit
code (V4.0x) was updated to 32 bit code (V4.2x+). The machine would
work fine for a while (it varied from minutes to a day or 2), then all
IP connectivity would just stop. I tracked it down to a faulty TCP/IP
upgrade that did not correctly update the x:\Mptn\Setup.Cmd file. Once
that was corrected, everything worked fine.

If I remember correctly, there is subtle difference in the format of
the ROUTE entries in this file between the 16 bit and 32 bit versions
of TCP/IP. If your machines have been upgraded, check out the contents
of this file with a working machine.

Good luck..............pk
 
Back
Top