> This issue can come from various problems or settings. That warning can
> indicate other issues [not just what it appears to show].
[quoted text clipped - 21 lines]
> limitations, so files larger than [or less than] 2gig may *time out* during
> transfer, and <4 gig files may not work at all.
| helooo
| at First i want say thx for reply my question...
[quoted text clipped - 3 lines]
|
| in here, iam the System Administrator.. (but iam stillnew...)
Oh. Okay, it takes time... do not mistake what I present below for/as
chastisment.
| ok
| i will give you little information about situation in here...
[quoted text clipped - 13 lines]
| but now disk quota i set to off, but few client still show this
| problem...
Good "quota off", or at least until you understand WHY it should be *turned
on* and how to determine what the individual segment's quotas should be.
Common networking suggestions would be to check the *firewalls*, routers,
and network access/allowance, and, as previously indicated, the individual
nodes for blockage. However, there are a number of other potential issues
such as master browsers [not *Internet* browsers], sub-network
configurations, routing, etc., which could be {apparently are} involved.
| and iam install new windows98 on the pc that have this problem..
| after finish installing windows, i don't install any software just
| driver lan card and
| i leave do nothing, few minutes show up this BSOD again..
For Win98 to connect to the others it MUST be updated. A new installation
[un-updated] will have difficulties IF it can connect at all [obviously this
is a complex/compound network-mixed systems and servers, and substantial].
XP to Win98 has its own issues, but you also have servers in the mix.
The initial network negotiations will [as it appears in your case] likely
cause memory errors. The servers and SQL [both already updated and requiring
compatible clients] are likely requiring what can not be presently supplied
by the issue nodes. One issue is that the newly updated/installed system has
apparently NOT been setup FOR access IN/TO the network..
| and i try to netstat command in few pc that have this error,
| although they don't comunicate with the server, they show this
[quoted text clipped - 5 lines]
| and with netstat command in the / when BSOD computer, few doesn't
| comunicate with server but with other client always..
Did you re-assign/re-new the issue computer(s) network access. The
*server(s)* will use the OS, computer name, network group, mac address, IP
and several other identifiers for network setup/allowance. IF they match
[old setup and NEW setup], though a new node installation, then the conflict
comes with the former node now assigned [attempted] a NEW server access,
though, if you have failed to pre-setup the network for this node's access
{IP, workgroup, etc.] this would be the place to start..
The fix could likely entail Completely Killing/removing the old node [all
traces/vestiges] from/on the server(s) and SQL, and assigning the NEW [new
installation and upgraded] node the access it needs on the server/network
AND in SQL _*HOWEVER*_
I will suggest STRONGLY, as you are new to administration, that you seek
help in an appropriate forum. Try the SQL groups AND server groups AND
Microsoft Tech Net.
| or may be infected with VIRUS... ?
|
| or may be when they communicating each other with another client in
| background ?
| (but i dunno what they do..)
Far to deep a discussion for this group. It is advisable for ANY
SYSOP/IT/Administrator to familiarize themselves with networking and server
information.
I would recommend the SQL and server groups AND checking Cisco and other
sites for basic networking administration.
| you says " monitor your network connection to see if there is traffic
| [not *just* a
[quoted text clipped - 3 lines]
| thanks in advance..
| Eka
*PLEASE** try in a group [Microsoft has several language specific groups
available] related to your issues. Server administration requires a level of
expertise. As you are apparently unfamiliar with many of the tools available
on the servers and the individual nodes/systems [such as netdom, netstat,
netdiag, rasdiag, rsdiag, bitsadmin, netmon, resmon, etc], I will again
suggest reviewing the proper forums and information FIRST.
IF, and only if, you actually are somewhat more familiar than you presently
indicate, then you should know how to check the network generally via route,
trace, ping, and other basic tools and concepts. However, I think you would
have then supplied a bit more information than what you have.
|> This issue can come from various problems or settings. That warning
|> can indicate other issues [not just what it appears to show].
[quoted text clipped - 30 lines]
|> --
|> _________

Signature
MEB
http://peoplescounsel.orgfree.com
--
_________