Network stopped working after firmware upgrade

[Mellon]

Yo!

I just noticed what seems to cause my problem with the network. I have recently bought SE's new mobil Xperia X1 (great phone btw) :-) but suddenly I got some problem with Active Sync aswell and after trying all the different setting I could come up with I noticed that when I had Active Sync connected with my phone the Popcorn stoped working
So when I disconnect my phone it start to work again.
Just thought I'd share my experience with this and hope it can help you sort things out.

Regards,
/Melone

[pe_andel]

Hello again. Here's an updated status of my situation of connecting to my NAS with the latest firmware.

* I have now tried the suggestion mentioned earlier to change my IP-range in my router from 192.168.0.xxx to 192.168.1.xxx. This had no effect. My PCH now has 192.168.1.165 and its gateway and DNS'es are pointing to my router at 192.168.1.1.

* I have also tried adding the share with host-name as well as IP. This had no effect.

* I have also tested to add a user to my NAS (instead of the default settings which leaves it open to everyone) and then assign that user and pw when adding the share on the PCH. This had an affect on the error message shown, but I still can't access it. With the user I now get "No workgroup found" error message. Without the user i get the request cannot be processed" error message. It should be noted that I can access the NAS from any of my computers without any problems both configured with the separate user account and also without.

* It should be noted that this ONLY applies when my PCH is trying to connect with my D-LINK DNS-323 NAS. Everything works fine connecting and playing movies from any of my computers or even my older Maxtor Storage NAS. However the DNS-323 is my "main" NAS with 3TB and thus the problem. It should also be noted for new readers that everything works with the DNS-323 with the previous firmware - the problems started when upgrading to the latest firmware.

* And Finally... When downloading the firmware released on 22 Aug 2008 and installing (downgrading) it on my PCH. The share to my DNS-323 NAS works instantly again!

Werner, is this the problematics that the technicians have already solved and that you're now beta testing. Or is this somethign else? Do you want me doing any other tests to help you investigating the problem further? One thing that occured to me (probably irrelevant but still) is that the DNS-323 NAS is setup using Raid 0 so the volume I'm connecting to is actually two harddrives combined into Raid 0. The older Maxtor NAS that I didn't have any problems with only has one HD and thus no Raid. It's probably not relevant but I just wanted to point that out.

Are you on to the problem? Will there be a fix shortly? Has someone else got any other ideas I can test?

Regards,
Pelle

[Ruinit]

Is there a fix for this I have a A-110 and the same thing has happened to me upgraded the firmware and now the network shares don't work

[SEELE01]

Hi,

I got the same problem also, I managed to work around the problem by changing the host name to IP address. Weird is that the problem shows in only 2 out of my 3 PCs. I cannot find any clue such that only one wasn't affected except for this, the 2 PCs that stopped working had numbers in the host name while the one working has all letters. Does any of your host names having problem have numbers?

It would seem PCH's samba client has problem resolving host names with numbers in it. Though I cannot verify this as I don't want to rename my host names just to confirm. Can anyone verify?

[r0d]

Ok problem is solved for me by replacing hostname by ip adress, works fine now

[pe_andel]

Problem was actually solved for me as well, I didnt' do any other changes than mentioned earlier. However I downgraded and then upgraded again via USB and then it worked!

Seems like the latest firmware wasn't applied correctly when downloaded by the PCH itself.... USB did the trick!

[Phillo]

(10-31-2008 09:07 AM)hedstrom Wrote:  Where can I find the privious firmware version?

http://www.popcornhour.com/download/A100...-A100.html

[p3ter]

I also have this problem. Tried most suggestions here; Disabling VMWare network adapters from my server, deleting & recreating the shares, changing from netbios name smb://server/share to ip address smb://192.168.0.nnn/share, changing PCH from dynamic to static IP, rebooting Router & PCH etc.

I have PCH A100, no hard disk, no USB devices, and using no other services apart from the SMB shares that were working fine in August firmware. (So for me, without SMB the PCH is junk...)

Server is XP Professional, static IP. Server & PCH are on the same subnet, network uses 192.168.0.x range, gateway & dns address is router address i.e. 192.168.0.1

One more clue for the developers - I noticed that the device appears to lose it's DCHP lease at exactly the same time as I try to connect to a SMB share. Refreshing my Dlink DIR-655 DHCP Client list shows the PCH (with no Hostname) but as soon as I try to browse a SMB share, it dissapears off the network.

There is also little or no network activity judging by the network lights on the PCH.

I will be downgrading now, this is not how i like to spend my weekends. At least the August firmware was predictably flaky, most issues could be solved with a reboot.

[p3ter]

(11-22-2008 12:42 PM)p3ter Wrote:  I will be downgrading now, this is not how i like to spend my weekends. At least the August firmware was predictably flaky, most issues could be solved with a reboot.

Back to August firmware now, and SMB shares are working fine.

[p3ter]

I noticed Chris57 in another thread referring to this thread and recommending to try a static IP. This didn't work for me, so I tried to summarize the different solutions tried in this thread with the level of success... This is the score as I see it:

11 users: Unresolved, or resolved by firmware downgrade
5 users: resolved by disabling other (virtual) adapters on the server, e.g. Vmware or Hamachi
4 users: workaround - changing from netbios name to IP address
1 user: fixed after changing DCHP assigned DNS server IP's to match router IP.
1 user: fixed itself after overnight power off/reboot
1 user: fixed itself after reapplying firmware upgrade.

So, for those looking in this thread for a solution, there is a 50% chance that 'downgrade' is your only working solution, 20% chance that 'disabling virtual adapters on your server' may resolve, and 15% chance that 'change to static IP' will resolve

I noticed a comment "this problem is fixed" by werner somewhere in this thread, it would be great to hear more about this since there appears to be very little that is consistent here (apart from, IT WORKED FINE BEFORE THE UPGRADE!)

[elziko]

(11-07-2008 11:59 AM)werner Wrote:  ok our engineers fixed that problem, we will start testing on beta firmware soon

I have the same problem that was temporarily fixed by disabling my VMWare adapters.

Are you saying my issue is fixed, or everybody's? Are you sure they are all of the same root cause?

[p3ter]

My SMB problem is now fixed as well And at last I now have an acceptable logical explanation.

I needed to uninstall Microsoft Windows XP Hotfix KB957097 (MS08-068: Vulnerability in SMB could allow remote code execution) to enable SMB shares to work with the October firmware. This is apparently a fix to a vulnerability that has been around for SEVEN years that M$ has only seen fit to fix now...

To see if removing this hotfix works for you, go to Control Panel, Add/Remove Programs, select 'Show Updates' check box, then look under 'Windows XP - Software Updates' for the 'Security Update for Windows XP (KB957097)', which was installed on or around 12th November 2008. Uninstall it, then try your SMB shares again.

Thanks to magicfab who found this solution!
Samba problem with KB957097 / MS08-068
Samba connection not working after update to latest firmware

The only last question is why does this behavior change in the November firmware? Considering the description of the vulnerability, my suggestion would be that for some reason browsing a network share in the November firmware does not supply the correct logon credentials the first time, and asks for something that does not exist (just like the smbrelay exploit does... http://www.xfocus.net/articles/200305/smbrelay.html ) The Microsoft patch recognizes this behavior as suspicious, and refuses to respond by sending the password hash for the default logged in user, causing the error.?

[Trebor]

My setup:
Netgear readynas nv+
D-link dir-655
PCH A-100
Nfs shares on the readynas.
With the latest firmware I couldn't connect to my nfs-shares on the readynas. It was only solved by downgrading to august fw.

[p3ter]

(11-26-2008 11:02 PM)p3ter Wrote:  My SMB problem is now fixed

Just to add some more confusion to this issue... My problem reoccured after 5 days, so I have downgraded again.
I can confirm that hotfix KB957097 has not been reapplied, no other changes to the PCH, router or network config.

[airjoe]

(12-02-2008 05:09 PM)p3ter Wrote:  Just to add some more confusion to this issue... My problem reoccured after 5 days, so I have downgraded again.
I can confirm that hotfix KB957097 has not been reapplied, no other changes to the PCH, router or network config.

Is anyone from PCH working to fix this issue?