Unable to share files over crossover cable anymore

Hi,

I've run into a problem with file sharing between my laptop and my desktop.
It used to work perfectly. What I do is connect the two computers through a
cross over cable. I connect from the desktop to the laptop by typing the ip
adress in the file manage box. so something like \\192.xxx.xxx.xxx\d$. This
used to bring up a login box (laptop is part of the company network). After
this I had access to all the files on the d-drive.

Now however it doesn't work anymore. I can still do a ping and that works, I
can even start a remote desktop connection and that works too. But a simple
filesharing connection is not possible.

I don't know if it matters but I've updated the laptop to SP3 but the
desktop is still SP2.

Any ideas for solving this a very welcome.

"Menl" <Menl@discussions.microsoft.com> wrote in message
news:C0418546-DE17-4433-97CA-6CF899B9FFF1@microsoft.com...
> Hi,
>
> I've run into a problem with file sharing between my laptop and my
> desktop.
> It used to work perfectly. What I do is connect the two computers through
> a
> cross over cable. I connect from the desktop to the laptop by typing the
> ip
> adress in the file manage box. so something like \\192.xxx.xxx.xxx\d$.
> This
> used to bring up a login box (laptop is part of the company network).
> After
> this I had access to all the files on the d-drive.
>
> Now however it doesn't work anymore. I can still do a ping and that works,
> I
> can even start a remote desktop connection and that works too. But a
> simple
> filesharing connection is not possible.
>
> I don't know if it matters but I've updated the laptop to SP3 but the
> desktop is still SP2.
>
> Any ideas for solving this a very welcome.

Your statement "simple filesharing connection is not possible" doesn't tell
us a great deal. What actually happens when you try?

Try the following:
- Click Start / Run / cmd {OK}
- Type this command:
net use Q: \\192.xxx.xxx.xxx\d${Enter}

By the way, your 192... addresses are internal addresses. They are invisible
to the rest of the world. There is no risk whatsoever in publishing them.
You'll probably find that you share those same addresses with thousands of
other people.

What I meant with that simple file sharing is the method I described in my
message.
I type the address of the laptop so \\192.168.0.192\d$ and after a while I
get the following error:
"\\192.168.0.192 is not accessible. You might not have permission to use
this network resource. Contact the administrator of this server to find out
if you have access permissions. There are currently no logon servers
available to service the logon request"


BTW the ping command and remote desktop still work!!

I used the net use command you suggested and got the error: "System error
1311 has occurred. There are currently no logon servers available to service
the logon request."

I hope this clarifies the issue

"Pegasus (MVP)" wrote:

>
> "Menl" <Menl@discussions.microsoft.com> wrote in message
> news:C0418546-DE17-4433-97CA-6CF899B9FFF1@microsoft.com...
> > Hi,
> >
> > I've run into a problem with file sharing between my laptop and my
> > desktop.
> > It used to work perfectly. What I do is connect the two computers through
> > a
> > cross over cable. I connect from the desktop to the laptop by typing the
> > ip
> > adress in the file manage box. so something like \\192.xxx.xxx.xxx\d$.
> > This
> > used to bring up a login box (laptop is part of the company network).
> > After
> > this I had access to all the files on the d-drive.
> >
> > Now however it doesn't work anymore. I can still do a ping and that works,
> > I
> > can even start a remote desktop connection and that works too. But a
> > simple
> > filesharing connection is not possible.
> >
> > I don't know if it matters but I've updated the laptop to SP3 but the
> > desktop is still SP2.
> >
> > Any ideas for solving this a very welcome.
>
> Your statement "simple filesharing connection is not possible" doesn't tell
> us a great deal. What actually happens when you try?
>
> Try the following:
> - Click Start / Run / cmd {OK}
> - Type this command:
> net use Q: \\192.xxx.xxx.xxx\d${Enter}
>
> By the way, your 192... addresses are internal addresses. They are invisible
> to the rest of the world. There is no risk whatsoever in publishing them.
> You'll probably find that you share those same addresses with thousands of
> other people.
>
>
>

I did a search on the error code I got using your suggestion of the use of
net use. The error code was 1311. I found something about using the wrong
credentials and the solution was to use the Map network drive on the tools
menu in explorer. The key was to click on logon as different user. I filled
in the right credentials and voila it worked.

Now it works as well the old way I used it. So I still don't know what
caused it to not work properly anymore but it is neverteless fixed.

Thank you

"Menl" wrote:

> What I meant with that simple file sharing is the method I described in my
> message.
> I type the address of the laptop so \\192.168.0.192\d$ and after a while I
> get the following error:
> "\\192.168.0.192 is not accessible. You might not have permission to use
> this network resource. Contact the administrator of this server to find out
> if you have access permissions. There are currently no logon servers
> available to service the logon request"
>
>
> BTW the ping command and remote desktop still work!!
>
> I used the net use command you suggested and got the error: "System error
> 1311 has occurred. There are currently no logon servers available to service
> the logon request."
>
> I hope this clarifies the issue
>
> "Pegasus (MVP)" wrote:
>
> >
> > "Menl" <Menl@discussions.microsoft.com> wrote in message
> > news:C0418546-DE17-4433-97CA-6CF899B9FFF1@microsoft.com...
> > > Hi,
> > >
> > > I've run into a problem with file sharing between my laptop and my
> > > desktop.
> > > It used to work perfectly. What I do is connect the two computers through
> > > a
> > > cross over cable. I connect from the desktop to the laptop by typing the
> > > ip
> > > adress in the file manage box. so something like \\192.xxx.xxx.xxx\d$.
> > > This
> > > used to bring up a login box (laptop is part of the company network).
> > > After
> > > this I had access to all the files on the d-drive.
> > >
> > > Now however it doesn't work anymore. I can still do a ping and that works,
> > > I
> > > can even start a remote desktop connection and that works too. But a
> > > simple
> > > filesharing connection is not possible.
> > >
> > > I don't know if it matters but I've updated the laptop to SP3 but the
> > > desktop is still SP2.
> > >
> > > Any ideas for solving this a very welcome.
> >
> > Your statement "simple filesharing connection is not possible" doesn't tell
> > us a great deal. What actually happens when you try?
> >
> > Try the following:
> > - Click Start / Run / cmd {OK}
> > - Type this command:
> > net use Q: \\192.xxx.xxx.xxx\d${Enter}
> >
> > By the way, your 192... addresses are internal addresses. They are invisible
> > to the rest of the world. There is no risk whatsoever in publishing them.
> > You'll probably find that you share those same addresses with thousands of
> > other people.
> >
> >
> >

The key to your problem is the error message you have now quoted. It looks
like your TCP/IP settings are incorrect. If you type the phrase "There are
currently no logon servers" into the second box of the advanced Google
search box then you get around 10,000 hits. One of those on the first page
is likely to have the answer for your problem.


"Menl" <Menl@discussions.microsoft.com> wrote in message
news:41D4C774-E57E-405C-B760-1F175CB5D71E@microsoft.com...
> What I meant with that simple file sharing is the method I described in my
> message.
> I type the address of the laptop so \\192.168.0.192\d$ and after a while I
> get the following error:
> "\\192.168.0.192 is not accessible. You might not have permission to use
> this network resource. Contact the administrator of this server to find
> out
> if you have access permissions. There are currently no logon servers
> available to service the logon request"
>
>
> BTW the ping command and remote desktop still work!!
>
> I used the net use command you suggested and got the error: "System error
> 1311 has occurred. There are currently no logon servers available to
> service
> the logon request."
>
> I hope this clarifies the issue
>
> "Pegasus (MVP)" wrote:
>
>>
>> "Menl" <Menl@discussions.microsoft.com> wrote in message
>> news:C0418546-DE17-4433-97CA-6CF899B9FFF1@microsoft.com...
>> > Hi,
>> >
>> > I've run into a problem with file sharing between my laptop and my
>> > desktop.
>> > It used to work perfectly. What I do is connect the two computers
>> > through
>> > a
>> > cross over cable. I connect from the desktop to the laptop by typing
>> > the
>> > ip
>> > adress in the file manage box. so something like \\192.xxx.xxx.xxx\d$.
>> > This
>> > used to bring up a login box (laptop is part of the company network).
>> > After
>> > this I had access to all the files on the d-drive.
>> >
>> > Now however it doesn't work anymore. I can still do a ping and that
>> > works,
>> > I
>> > can even start a remote desktop connection and that works too. But a
>> > simple
>> > filesharing connection is not possible.
>> >
>> > I don't know if it matters but I've updated the laptop to SP3 but the
>> > desktop is still SP2.
>> >
>> > Any ideas for solving this a very welcome.
>>
>> Your statement "simple filesharing connection is not possible" doesn't
>> tell
>> us a great deal. What actually happens when you try?
>>
>> Try the following:
>> - Click Start / Run / cmd {OK}
>> - Type this command:
>> net use Q: \\192.xxx.xxx.xxx\d${Enter}
>>
>> By the way, your 192... addresses are internal addresses. They are
>> invisible
>> to the rest of the world. There is no risk whatsoever in publishing them.
>> You'll probably find that you share those same addresses with thousands
>> of
>> other people.
>>
>>
>>