Network stopped working after firmware upgrade

[mercucho1]

my pch doesnt work smb too

- Operating system
Windows XP SP2 and Windows Vista SP1

- Router model
Thomson TCW690

- How is your NMT connected to the rest of the network?
ethernet

- What settings do you have on the network setup pages of the NMT.
IP 192.168.0.11
255.255.255.0
192.168.0.1
dns1 202.188.0.113
dns2 202.188.1.5

[werner]

can you change your DNS to your Router IP which i think should be 192.168.0.1? cahnge both DNS to this IP, after that reboot also

(11-01-2008 03:56 PM)mercucho1 Wrote:  my pch doesnt work smb too

- Operating system
Windows XP SP2 and Windows Vista SP1

- Router model
Thomson TCW690

- How is your NMT connected to the rest of the network?
ethernet

- What settings do you have on the network setup pages of the NMT.
IP 192.168.0.11
255.255.255.0
192.168.0.1
dns1 202.188.0.113
dns2 202.188.1.5

[Blubebox]

I've got the same problem, and figured out that everything worked as supposed again after I shut down and disabled Hamachi on the server.
The server and PCH are on the same home network (a router in between) and Hamachi on the server is for friends access.
So I got the "Request cannot be processed" on PCH after upgrading to this latest fw, and when I disabled Hamachi on the server everything worked as it supposed.

Does this help anyone in figuring out what the problem is? How can I use Hamachi again at the same time as PCH?

EDIT: System setup:
Server: XP SP2, standard network share (smb), hamachi running.
Router: dlink dgl 4300 with 2 computers, PS3 and PCH

[r111]

removed all network shares. added NFS and SMB. NFS works fine. SMB does not work. SMB machine is Vista Home SP1.

[mercucho1]

(11-01-2008 05:53 PM)werner Wrote:  can you change your DNS to your Router IP which i think should be 192.168.0.1? cahnge both DNS to this IP, after that reboot also

WOW!! Perfect!!

Thanksssssss

[luojs]

Change the hostname to vista pc's IP address fixed my problem.

[r111]

(11-01-2008 07:25 PM)r111 Wrote:  removed all network shares. added NFS and SMB. NFS works fine. SMB does not work. SMB machine is Vista Home SP1.

I'm using the IP address for my Vista box and is still doesn't connect. I can also browse to my Vista shares but then cannot access any files - just times out.

[hedstrom]

(11-01-2008 06:36 PM)Blubebox Wrote:  I've got the same problem, and figured out that everything worked as supposed again after I shut down and disabled Hamachi on the server.

Read your post about Hamachi and found out a connection. I have also got a viritual network on my server. I have VM-Ware on my server and when I disabeled my viritual network adaptors it started to work.

[dinauktion]

(11-02-2008 08:19 AM)hedstrom Wrote:  

(11-01-2008 06:36 PM)Blubebox Wrote:  I've got the same problem, and figured out that everything worked as supposed again after I shut down and disabled Hamachi on the server.

Read your post about Hamachi and found out a connection. I have also got a viritual network on my server. I have VM-Ware on my server and when I disabeled my viritual network adaptors it started to work.

Great job Hedstrom, now to find out what your vna did? Check if the error comes back if you enable it again, maybe do a complete reinstallation of the vm?

[hedstrom]

Well. It's not the network adaptors. It's the VM-ware service. If I disable the VM-Ware adaptors the service automaticly stops and it starts to work. If I then enable the adaptors it still works. But if I start the VM-ware service the error returns.

Same problem after reinstalling WM-ware. And I have tested two diffrent versions of VM-ware with the same problem.

Whats diffrent in the new firmware that causes this error? I can't uninstall VM-Ware. I have several viritual servers that I need for work.

[dinauktion]

(11-02-2008 09:03 AM)hedstrom Wrote:  Well. It's not the network adaptors. It's the VM-ware service. If I disable the VM-Ware adaptors the service automaticly stops and it starts to work. If I then enable the adaptors it still works. But if I start the VM-ware service the error returns.

Same problem after reinstalling WM-ware. And I have tested two diffrent versions of VM-ware with the same problem.

Whats diffrent in the new firmware that causes this error? I can't uninstall VM-Ware. I have several viritual servers that I need for work.

Well that's beat me, maybe Werner has an answer for this. Is there any security setting in the VM ware? I use VPN for my work which creates an encrypted tunnel to the server, TCP/IP or UDP transport but this is not the same case. Actually if your adapter creates a virtual network, then there will be some interference between the Workgroup SMB settings. I know I can not see my office computer when using it with VPN from the PCH side.

[.jcj.]

Confirmed. One cause of the SMB problem is VMWARE.

After upgrading to the latest fw, I couldn't access my shares with the network browser provided on the popcorn main menu.

I disabled all VMWare* Services, restarted my PC and popcorn hour, but no change.

Then I disabled all my 'VMware Network Adapter VMnetxx', an I could access my shares through the network browser again.

Server: Windows XP SP3
VMWare Workstation 6.0

[werner]

hmm interessting find i will ask our engineers on monday

[XTof]

(11-02-2008 12:40 PM).jcj. Wrote:  Then I disabled all my 'VMware Network Adapter VMnetxx', an I could access my shares through the network browser again.

Thx a lot, disable Network Adapter did fix my SMB access

[matth]

(11-01-2008 02:47 AM)cheaper_popcorn Wrote:  Can you please give us some more details of your setups guys?

The following info will be helpful in order to see if the problem has any common denominators:

- Operating system
- Router model
- How is your NMT connected to the rest of the network?
- What settings do you have on the network setup pages of the NMT.

From what I've read it sounds like the problem could somehow be related to the DNS Server settings.

I would start with checking the DNS configuration on the NMT as well as your other devices, and make sure that they all have the same DNS server(s) specified.

Also, it generally is a better idea to setup the entire network for manual, static IP addresses rather than DHCP, because with DHCP when IP addresses get switched around, you may run into problems.

Quote:this sucks big time I want to start using the yam plugin and now this...

Just to check, when you say 'using the YAMJ plugin' do you mean the plugin for Myihome, or do you mean YAMJ in general?

The Myihome YAMJ plugin works normally for me. The network problems reported in this thread don't appear to have anything to do with Myihome.

I am having similar issues in that I can't browse or access SMB / NFS shares on the last 2 FW releases. June08 works OK.

Windows XP SP3
Dlink DI-524
PCH -> ethernet -> Dlink -> ethernet -> PC
IP - 192.168.0.200 (static)
Subnet 255.255.255.0
Gateway 192.168.0.2
DNS1 192.168.0.2
DNS2 192.168.0.2
PC IP 192.168.0.201 (static)
Web access works fine, myihome works fine