Last week I did a reinstall of Win7 x64 on my machine. It has been since Win 7 went gold that I have reinstalled (I love a clean system), and it was far longer than my 12 month cycle that I have usually stuck to for some time.

 

Since January-ish, I have been running an unraid server off of a flash disk with ZERO pain and zero effort. It's a fantastic product. I purchased a key also... FYI

 

Here's my problem. Please understand I did my best to search the forums for an answer, but I was actually having trouble settling on the correct KEYWORDS to use for the search...

 

Now that I have reinstalled windows, I had about 5 days where windows easily saw and communicated with my unraid server - both in the file explorer and in the web gui.

 

However over the last week or two, I am no longer able to find the server \\tower\ via the file explorer. I am able to connect to it's (manually configured) ip address in the web browser and I have no problem accessing and working within the gui.

 

I cannot access the web gui by directing my browser to \\tower\, however.

 

I have tried ipconfig /flushdns and also nbtstat -RR, neither of which worked.

 

Power cycles on both my desktop and the server have yielded nothing, either.

 

I'm at a loss here... Dunno what to do.

 

I use OPENDNS for my dns (have always done so with no problem), and I also use HAMACHI on my windows machines (have always done so with no problem).

 

I have introduced no new networking settings or softwares that I can conceive would create this issue!

 

Please advise.

 

 

VERSION:  4.6 "unRaid Server Plus"

Log:

unraid_nas_log.txt

Can you access the shares via IP address?

I apologize, but I'm not aware of how to do this.. When I get home from work I'll try going to win explorer and just typing the tower ip into the address bar?

 

rather than "\\tower\"  i'll type  "192.168.1.125"

 

will give it a whirl and followup, thanks.

Okay, good news.

 

\\192.168.1.125\share  works instantly in file explorer.

 

 

So, I have no problem setting up a mapped network drive connecting directly to the IP address, but for my own edification... can anyone explain to me what went wrong and what the correct steps to solve the problem are?

Look for the Hosts file in this path.

C:\WINDOWS\system32\drivers\etc

 

create a line like this

192.168.x.x  tower

 

change tower for your tower name.

 

x=change for Ip numbers.

 

then this will fix the routing to the ip from the name.

What would have happened for it to stop working automatically? Is there not a command prompt way to reset something so it would be working again naturally?

 

I would like to know in case I have a problem with another network computer some time down the road..

 

Thanks

There are a lot of different services that need to be set to start automatically in Win 7 for it to work and even then operation does not seem to be guaranteed. The method that always seems to work if connecting via IP address and then mapping the drive.

 

Here are the required services that I know about:

--SSDP Discovery

--TCP/IP NetBIOS Helper

--Computer Browser

--Server

--Link-Layer Topology Discovery Mapper

 

There may be some that I don't know about.