For the last couple years, I've owned a Linksys WRT54G wireless router. And for the last 4 months I've used the same router as a means of networking my main rig with my gaming server. I use Remote Desktop to administrate the server, and when I normally log onto the server, I use its UNC name "Blackbox" to connect to it rather than its IP addy. I also used the UNC name to connect to network resources between computers, i.e. "\\blackbox\blahblah\".

Today, I tried upgrading my router firmware to one of the DDwrt sources, which was stupid anyway because I've tried dozens of times to upgrade the thing and it's never worked in the past, even with official Linksys .bin files. So anyway, I tried upgrading the firmware, only to have it tell me "Upgrade are failed!". So I think no big deal, and go about my business.

So then, I try remote desktoping my server the way I always have, only for it to tell me that the computer couldn't be found. But I try connecting with the IP of the server, and that worked! I also tried accessing the server with the UNC paths "\\blackbox", but that wouldn't work either. So I then tried "\\192.168.1.103" (the IP it has on the router) and that worked like a charm. It seemed as though the UNC naming system wasn't working. To test it out for sure, I tried adding a network resource on my main rig, using the UNC address "\\192.168.1.103\downloads" which is a folder I keep a bunch of files in on the server. My main rig added the network folder alright, but the folder was listed in My Network Places under "The Internet", and not "Local Network". My router thinks my local network is the internet!!!

Any ideas on what happened?

maybe you bricked the router after that update. i remember that mine was being a b*tch with updating, and i went through like 4 routers until the update accually went through.

Quote: Originally Posted by Jobistober For the last couple years, I've owned a Linksys WRT54G wireless router. And for the last 4 months I've used the same router as a means of networking my main rig with my gaming server. I use Remote Desktop to administrate the server, and when I normally log onto the server, I use its UNC name "Blackbox" to connect to it rather than its IP addy. I also used the UNC name to connect to network resources between computers, i.e. "\\blackbox\blahblah\". Today, I tried upgrading my router firmware to one of the DDwrt sources, which was stupid anyway because I've tried dozens of times to upgrade the thing and it's never worked in the past, even with official Linksys .bin files. So anyway, I tried upgrading the firmware, only to have it tell me "Upgrade are failed!". So I think no big deal, and go about my business. So then, I try remote desktoping my server the way I always have, only for it to tell me that the computer couldn't be found. But I try connecting with the IP of the server, and that worked! I also tried accessing the server with the UNC paths "\\blackbox", but that wouldn't work either. So I then tried "\\192.168.1.103" (the IP it has on the router) and that worked like a charm. It seemed as though the UNC naming system wasn't working. To test it out for sure, I tried adding a network resource on my main rig, using the UNC address "\\192.168.1.103\downloads" which is a folder I keep a bunch of files in on the server. My main rig added the network folder alright, but the folder was listed in My Network Places under "The Internet", and not "Local Network". My router thinks my local network is the internet!!! Any ideas on what happened?

I wouldnt blame it on the router, I would say reinstall DD-WRT or open-WRT. I love my linksys router. It would be a piece without the open firmware.

Unplug your router, hit the reset button a few times, eat a sandwich, call your mom, plug in your router, reconfigure all your settings that you remember. that should get it working

LINKSYS FTW!!

Well I did some poking around, researched openWRT a bit, and found out that Linksys WRT54G v5 and later routers are built with a proprietary OS unlike the Linux-based OS in the earlier versions. So there is no openWRT firmware for v5 and later models... and guess what version my router is? Version 5!

So I went to Linksys's website and just downloaded their latest firmware version for my specific router and tried upgrading again, and it actually worked. However, I still experience the same problems as before. Guess it's time for Chrome's technique

Sell it on ebay, buy an older version, get dd-wrt, never worry about this problem again. Just an idea haha.

Quote: Originally Posted by post_break Sell it on ebay, buy an older version, get dd-wrt, never worry about this problem again. Just an idea haha.

Wanna sell me yours? Just messin'. I'm really not all that worried about it... maybe I'll just live with it. Or maybe I'll get a nicer router.