NIC disconnecting frequently

  • Thread starter Thread starter Shibin John
  • Start date Start date
S

Shibin John

Hi guys,

I am an Administrator of a leading bank. My issue is, my
pc's NIC is getting disconnected frequently. The funny
thing is, our main program is running on HP unix, I can
access our main program through telnet session, but can't
access neighbourhood pc's or printers. When I restarting
my machine, it will work perfectly and after a half of one
hour, it is getting disconnected automatically. Any
solutions?? Can you tell me, how can we check the NIC? is
there any s/w like amidiag. My PC's Compaq deskpro with
windows 2000 professional. The NIC is integrated one. Pls
give me a solution.

Rgds
Shibin
 
It is possible that the other computer [server] is disconnecting you. Windows 2000/XP
Pro/2003 will by default disconnect idle sessions connected to it after 15 minutes as
shown in Local Security Policy/security settings/local policies/security options.

Other things that may help are to configure your network adapter to use the actual
network speed instead of "auto" in it's properties. There is a support tool called
netdiag that can be run on a Windows 2000 computer. You also could try installing a
new nic in your computer and disable the onboard one in cmos properties. Don't rule
out a flaky CAT cable or switch port either if using a desktop that always uses the
same cable and port.. -- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;321708
 
I am having the same problem. I have a desktop that is
using Windows XP and connect to a Windows 2000 server.
It seems to just randomly disconnect. I have some music
stored on my server and can be listening to it on my
workstation and suddenly it disconnects. I can go to the
server and disable the NIC and enable it and it will
reconnect without rebooting. I have even replaced NICs.
Any help would be greatly appreciated.
Jason
-----Original Message-----
It is possible that the other computer [server] is
disconnecting you. Windows 2000/XP
Pro/2003 will by default disconnect idle sessions
connected to it after 15 minutes as
 
There are known issues with SMB signing between Windows 2000 and XP Pro in certain
cases that can cause irregular network connectivity. Assuming that none of your
network computers are configured to require SMB signing with the "always" security
option configured in their effective settings in Local Security Policy you can
configure your Windows 2000 server to not use SMB signing. In Local Security Policy
of the server [or Domain Controller Security Policy for domain controllers] go to
security settings/local policies/security options and disable [not to undefined] the
four security options for "digitally sign communications". Then run secedit
/refreshpolicy machine_policy /enforce on the Windows 2000 server. the link below
explains this some more. --- Steve

http://www.jsiinc.com/SUBL/tip5800/rh5874.htm

Jason Adams said:
I am having the same problem. I have a desktop that is
using Windows XP and connect to a Windows 2000 server.
It seems to just randomly disconnect. I have some music
stored on my server and can be listening to it on my
workstation and suddenly it disconnects. I can go to the
server and disable the NIC and enable it and it will
reconnect without rebooting. I have even replaced NICs.
Any help would be greatly appreciated.
Jason
-----Original Message-----
It is possible that the other computer [server] is
disconnecting you. Windows 2000/XP
Pro/2003 will by default disconnect idle sessions
connected to it after 15 minutes as
shown in Local Security Policy/security settings/local policies/security options.

Other things that may help are to configure your network adapter to use the actual
network speed instead of "auto" in it's properties. There is a support tool called
netdiag that can be run on a Windows 2000 computer. You also could try installing a
new nic in your computer and disable the onboard one in cmos properties. Don't rule
out a flaky CAT cable or switch port either if using a desktop that always uses the
same cable and port.. -- Steve

http://support.microsoft.com/default.aspx?scid=kb;en- us;321708




.
 
Sorry, dear friend,

I tried all these options. Now the system is not
connecting to the n/w printer. But the same time, one of
my printer which is connected to Unix server /
applications, can take the printouts. Eventhough all the
n/w printers showing the status ready, while taking a test
printouts, it is giving error named, unable to connect to
the printer. But same time, I can access neighbourhood
pc's and applications. Surprisingly, there is no error in
event viewer also. Any solutions.........

Thanks and regards
Shibin
 
Back
Top