Hi All,
I installed my IM-based drivers on two of the machines and tried to
communicate between them. Ping, transfering small files work fine. But when
I try to access (remotely) directories of the other machine, then after
trying for some time, windows gives error: “Can’t copy X: The Specified
network name is no longer available”.
I checked the Event Log of my machine, but it doesn’t reveal anything.
Has anybody faced this kind of problem ?
Any kind of clue will be much appreciated.
regards
Amit
Does you NDIS IM driver modify packets? If son then the PCAUSA article
“KB05280101 - Modifying NDIS Intermediate (IM) Drivers And NDIS
Task-Offload” at the URL http://www.ndis.com/pcakb/default.htm may help.
–
Thomas F. Divine
PCAUSA - Toolkits & Resources For Network Software Developers
NDIS Protocol - NDIS Intermediate - TDI Client/Filter
http: - http:
“Amit Manocha” wrote in message
news:xxxxx@ntdev…
>
> Hi All,
>
> I installed my IM-based drivers on two of the machines and tried to
> communicate between them. Ping, transfering small files work fine. But
when
> I try to access (remotely) directories of the other machine, then after
> trying for some time, windows gives error: “Can’t copy X: The Specified
> network name is no longer available”.
> I checked the Event Log of my machine, but it doesn’t reveal anything.
>
> Has anybody faced this kind of problem ?
> Any kind of clue will be much appreciated.
>
> regards
> Amit
>
>
>
></http:></http:>
Thomas,
Thanks for your response. Yes, I am modifying the packets.
As said in that paper, I changed my code. but still it is giving the same
problem.
To give a more deeper insight into the problem, this problem only occurs
when I post-process the larger files. If I don’t do the post-processing,
everything works finely. I am doing the post-processing in PtReceiveComplete
handler.
What can be the problem ? Can it be the time taken in post-processing ?
Thanks once again.
Amit Manocha
“Thomas F. Divine” wrote in message news:xxxxx@ntdev…
>
> Does you NDIS IM driver modify packets? If son then the PCAUSA article
> “KB05280101 - Modifying NDIS Intermediate (IM) Drivers And NDIS
> Task-Offload” at the URL http://www.ndis.com/pcakb/default.htm may help.
>
> –
> Thomas F. Divine
>
> PCAUSA - Toolkits & Resources For Network Software Developers
> NDIS Protocol - NDIS Intermediate - TDI Client/Filter
> http: - http:
>
> “Amit Manocha” wrote in message
> news:xxxxx@ntdev…
> >
> > Hi All,
> >
> > I installed my IM-based drivers on two of the machines and tried to
> > communicate between them. Ping, transfering small files work fine. But
> when
> > I try to access (remotely) directories of the other machine, then after
> > trying for some time, windows gives error: “Can’t copy X: The Specified
> > network name is no longer available”.
> > I checked the Event Log of my machine, but it doesn’t reveal anything.
> >
> > Has anybody faced this kind of problem ?
> > Any kind of clue will be much appreciated.
> >
> > regards
> > Amit
> >
> >
> >
> >
>
>
>
></http:></http:>
I agree NetMon is essential. Unfortunately, if one is modifying packets,
it appears – at least if the IM driver is based on passthru – that
NetMon sees packets before the IM’s Send function and after the IM’s
Receive function. That can be quite confusing.
Is there a way to ensure NetMon reports what was sent over the wire?
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini
Windows DDK MVP
Run NetMon or Sniffer Or EthReal on another machine which is on the same
subnet/hub. If you have a switch you may not see all packets, so the key
is use hub for sniffing traffic.
-Srin.
-----Original Message-----
From: James Antognini [mailto:xxxxx@mindspring.nospam.com]
Sent: Monday, July 21, 2003 2:19 PM
To: Windows System Software Developers Interest List
Subject: [ntdev] Re: Windows Error: “The Specified network name is no
longer available”.
I agree NetMon is essential. Unfortunately, if one is modifying
packets,
it appears – at least if the IM driver is based on passthru – that
NetMon sees packets before the IM’s Send function and after the IM’s
Receive function. That can be quite confusing.
Is there a way to ensure NetMon reports what was sent over the wire?
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini
Windows DDK MVP
You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Another option is to use an XP machine with two NICs and bridge them together, run netmon on it, and connect it between the PC with the IM driver and a hub. Of course, this won’t work with dial-up adapters as far as I know.
Regards,
Ed Lau
ArteraGroup, Inc.
900 Straits Tpke
Middlebury, CT 06762
----- Original Message -----
From: James Antognini
Newsgroups: ntdev
To: Windows System Software Developers Interest List
Sent: Monday, July 21, 2003 5:19 PM
Subject: [ntdev] Re: Windows Error: “The Specified network name is no longer available”.
I agree NetMon is essential. Unfortunately, if one is modifying packets,
it appears – at least if the IM driver is based on passthru – that
NetMon sees packets before the IM’s Send function and after the IM’s
Receive function. That can be quite confusing.
Is there a way to ensure NetMon reports what was sent over the wire?
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini
Windows DDK MVP
You are currently subscribed to ntdev as: xxxxx@midcore.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Well, yes, that would work. Rather expensive. It might make more sense,
in cost, to get a relatively cheap router with a mini OS that supports
packet logging. Of course, that solution might be more expensive in
terms of time to find a router, learn/configure the OS, etc.
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini
Windows DDK MVP