Re: Network share question
- From: jmm <jmm@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 1 Apr 2005 02:25:04 -0800
"Herb Martin" wrote:
> "jmm" <jmm@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:9504EA09-5385-4C60-91A3-B35C5221A06F@xxxxxxxxxxxxxxxx
> >
> >
> > "Herb Martin" wrote:
> >
> > > "jmm" <jmm@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:28FCF610-F48B-45E1-A2C2-C4C434F1DAE6@xxxxxxxxxxxxxxxx
> > > > Hi,
> > > > I have shared a folder for administrative purpose on my w2k sp4 server
> > > > yesterday and there is something wrong when i try to use it.
> > > > The server and the workstation's are in the same network.
> >
> > > > After a reboot of the server some workstation can immediately make use
> of
> > > > the share and some others after some times (1 or 2 or 3 hours(s)).
> > >
> > > Since this seldom if ever happens due to the
> > > share itself, one must look for other intermittent
> > > issues, such as:
> > >
> > > Hardware -- bad cables, hubs, NICs.
> > >
> > > DNS, i.e., internal and [incorrectly] external DNS servers
> > > specified on client or DC NICs
> > >
> > >
> > > > I try to understand what's going wrong, is there some mysterious
> network
> > > > problem that i can't see ?
> > >
> > > What DNS servers do all of your internal machines
> > > specify on their NICs ? (Do NOT mix external DNS
> > > there.)
> > >
> > > How about other things, like direclty testing name
> > > resolution or ping when you experience such problems?
> > >
> > > > or is it my windows server that have some problems.
> > > > Can anybody help me to find on which way to search ?
> > >
> > > Be systematic. Prove what works. Look for what doesn't
> > > work.
> > >
> > > Post the IPConfig /all for an affected machine.
> > > (paste the text, don't type it, and don't use a graphic.)
> > >
> > > Show us what you get if you type:
> > >
> > > net view \\ServerName
> > >
> > > net use * \\ServerName\ShareName * /user:DomainOrServer\Username
> > >
> > > DomainOrServer = the name of the domain OR the server where the
> > > Username account is valid.
> > >
> > >
> > > Hi,
> > Sorry to answer so late but have a lot of job.
> > I have made a check of the cables and seen nothing abnormal.
>
> When I mention bad cables it would likely take
> a cable tester to be sure.
>
> > At level of the DNS i have ask to architecture to make a check of DNS file
> > and all that stuff and everything seems to be ok.
>
> That is not likely sufficient -- running the test tools like
> DCDiag and/or DNSLint is pretty much a necessity to
> prove the DNS Servers are setup correctly.
>
> And DNS clients can be wrong on their own.
>
> > Yes all of our internal machines ont their NIC's
>
> ???
>
> > No problem at level of ping or and the name resolution is good.
> > here is the result of the ipconfig /all
>
> This is not always sufficient for internal, especially AD purposes.
>
> > C:\Documents and Settings\a222401>ipconfig /all
> >
> > Windows 2000 IP Configuration
> >
> > Host Name . . . . . . . . . . . . : CN1423
> > Primary DNS Suffix . . . . . . . :
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : Crelan.be
> >
> > Ethernet adapter Local Area Connection:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network
> > Physical Address. . . . . . . . . : 00-30-05-3F-3D-69
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 10.1.3.4
> > Subnet Mask . . . . . . . . . . . : 255.255.0.0
> > Default Gateway . . . . . . . . . : 10.1.7.53
> > DNS Servers . . . . . . . . . . . : 10.1.6.25
> > 10.1.6.122
> > 10.1.6.124
>
> Do each and every one of those DNS servers resolve the
> server when you query them explicitly (and when the
> problem presents)?
>
> nslookup hn016.Crelan.be 10.1.6.25
> nslookup hn016Crelan.be 10.1.6.122
> nslookup hn016Crelan.be 10.1.6.124
>
> BTW, are you in Belize? I love that place.
>
> > here is the net view \\hn016
> > C:\Documents and Settings\a222401>net view \\hn016
> > Shared resources at \\hn016
> > Share name Type Used as Comment
> > --------------------------------------------------------------------------
> -----
> > C Disk
> > D Disk
> > LOGS Disk
> > The command completed successfully.
>
> Then the network and name resolution is working
> for the above.
>
> Does it still work (this well) when you experience the problem?
>
> > Here is the net use of the share
> > C:\Documents and Settings\a222401>net use * \\hn016\unishare$ *
> > /user:crelan\a22
> > 2401
> > Type the password for \\hn016\unishare$:
> > Drive F: is now connected to \\hn016\unishare$.
> > The command completed successfully.
>
> All above it working.
>
> > But like i said upper in this treat after some times everything is working
> > fine.
> > and what do you have ask to send is not very representative of the problem
> > that i have because now i can access the share without any problem, it's
> only
> > when i initiated a reboot.
>
> I intended you would try the above when the problem presents;
> although doing it now allows you to compare the working
> results with what is (later) returned during problems.
>
> No, i'm not in belize, i'd love to be there but i'm living in belgium.
no sun but rain a lot.
When the problem occurs i will try to use the information you give me
let you know if found something
>
.
- Prev by Date: RE: Can't Connect to FTP Folders
- Next by Date: SNMP service consuming large amounts of memory until server stops
- Previous by thread: replication software
- Next by thread: SNMP service consuming large amounts of memory until server stops
- Index(es):
Relevant Pages
|
