"Error Code: 0x80070035" When trying to connect to home server.

[Maximilian]

However it will work if i try to connect get that error then leave it for a minute or so and try again... its strange. If i get the error and keep trying without leaving it then it will not work, it seems to need time before it connects.

When i say connect i mean double click on "MAXSERVER" here:

I can remote desktop into it instantly though, never any error or delay there. What gives? Everyone else with this error code on google seems to not be able to connect at all which is different to this, its more of an annoyance than anything.

 

[dave_the_nerd]

Is it the server in your sig?

Is it just a delay for drive spin-up?

Edit: nah, probably not.

RDP is a different protocol. What connection type is failing - file sharing?

That error message means network path not found. Is the server DHCP or static? Do you have an alias to it in your hosts file? Local DNS or just ISP/External?

 

[MrColin]

That error message means network path not found. Is the server DHCP or static? Do you have an alias to it in your hosts file? Local DNS or just ISP/External?

If this is the case you can fix it easily by setting a fixed IP on the server and either a local DNS entry for it or a line in the client hosts file

 

[Maximilian]

Is it the server in your sig?

Is it just a delay for drive spin-up?

Edit: nah, probably not.

RDP is a different protocol. What connection type is failing - file sharing?

That error message means network path not found. Is the server DHCP or static? Do you have an alias to it in your hosts file? Local DNS or just ISP/External?

Yeah its the server in my sig, OS is on the SSD. This is what i see when i access it successfully:

Yeah file sharing.

I dont know if its static, ive got it on a fixed IP, 192.168.0.2, its always assigned that by the router. I guess thats static?

Dont know what a hosts file is or an alias.

Local DNS, my desktop is connected to the WNDR3700 router downstairs via LAN cable, the server is connected via LAN cable to the same router, it sits next to the router.

 

[Maximilian]

Anyone have any more ideas? My windows 7 laptop dosent seem to have this issue, it will connect right away. It uses a wireless connection.

 

[QuietDad]

It's a known bug in Windows 7. Windows 7 Explorer has issues with DNS and name resolution. http://answers.microsoft.com/en-us/...-windows/84791143-b70a-4ec2-b700-98df657fe45c

 

[Maximilian]

It's a known bug in Windows 7. Windows 7 Explorer has issues with DNS and name resolution. http://answers.microsoft.com/en-us/...-windows/84791143-b70a-4ec2-b700-98df657fe45c

Hmmmmmmm interesting!

Ill give the solution a shot, just tried \\192.168.0.2 and it connected straight away after giving the credentials, heres hoping its fixed