Query about setting up network

[dmcconnell]

Newbie question about setting up a network.

I have a combined wireless adsl/router (netgear 834G) connected to a desktop PC via ethernet (router IP is 192.168.0.1, PC NIC is 192.168.0.2).
Wireless is turned on and I can connect a laptop (IP 192.168.0.3) wirelessly to the internet.
I also have an Asus w500g wireless router that I want to eventually connect to a Topfield PVR.
I cannot see the desktop from the laptop or vice-versa.
What am I doing wrong?
Do I need another NIC in the desktop connected into the router in order to be onto a network, or to run a hub from the router back to teh desktop?

Any help appreciated.
Thanks

[Cavalier90]

This is usually due to the firewalls on the PC and laptop not allowing outside viewing. You need to set up the other machines' ip addresses on the other computer in the trusted zone. Can you do this? If not what firewalls are you using and we may be able to suggest how?

You also need to enable the folders for sharing by a workgroup (this presumes you are using Windows).

[dmcconnell]

Yes both are using windows xp pro.
I'm really not sure what I am doing. The desktop has the windows firewall enabled, and the router has a firewall as well. I dont think the laptop has anything running.
All drives on the computers have had sharing enabled.

[Cavalier90]

Check the laptop by going into Start - Control Panel and select Windows Firewall. That should tell you whether your laptop is running a firewall.

[dmcconnell]

The desktop has the windows firewall enabled but the laptop doesn't (box not ticked in Internet Connection Firewall on teh advanced tab for the wireless network connection.

[Cavalier90]

The desktop firewall needs chcking. Go to Start - Control Panel - Windows Firewall. Open the Exceptions tab. There should be a tick in the File and Print sharing box. If not this is the reason the files cannot be seen.

I would actually disable the Windows Firewall and install a better one such as ZoneAlarm that is free from www.zonelabs.com. If and when you have done this, post back and we'll guide you on how to configure that firewall to allow file sharing.

[dmcconnell]

The file and print sharing exception is already ticked.
Im downloading the zonealarm firewall now.

Can I just check that the way I have these connected is the correct way as I have seen info suggesting that 2 NIC are required?

[dmcconnell]

Ive installed zonealarm now

[Cavalier90]

The connections you describe at the start of the thread seems OK, until you mention the Asus router. I am assuming that the Asus router is not part of the equation yet. I am also not sure about connecting the PVR to a router as the description I found only describes a USB connection. For the PVR to be able to use a router I would expect it to have a NIC or wireless card so that it could support an ip address and form part of the network. Someone more knowledgeable may correct me.

[Cavalier90]

With Zonealarm go to Firewall tab on the left of the box, Zones tab at the top of the box, and "add" the ip address of the laptop as a trusted site.

[dmcconnell]

The asus is definitely not part of the equation yet. That gets hugely more complicated by flashing its firmware to be a linux ftp server which is way beyond me.

Zonealarm has replaced windows firewall on the dsektop, and so far has blocked 680 intrusions!

[dmcconnell]

Have added the laptop IP as described.

[Cavalier90]

Hells teeth!!!!

Do you have the firewall in the netgear ADSl/router activated? This should stop most of those before they hit the desktop.

[Cavalier90]

Can the laptop now view the desktop files?

[dmcconnell]

In network places on the desktop, I can now see and access the hard drive and shared folders on the laptop.

On the laptop, there are only the laptop shared items. I now have an icon for an internet gateway.

[Cavalier90]

Next question, are both machines part of the same Windows workgroup?

[dmcconnell]

The firewall on teh router does seem to be active.
I had added 2 exceptions to it to enable emule to work (which isn't running at the moment). The intrusion alarm is now over 1500!?!

[dmcconnell]

Next question, are both machines part of the same Windows workgroup?

I think so - just went for the default setting (MSHOME) when running the network wizard. But I ran that about 20 times in the last couple of days

[dmcconnell]

I can now see the desktop in Workgroup computers but it wont let me access it. The error message mentions access restrictions?

[Cavalier90]

Can you view the router firewall log to see what is being stopped? My Zonealarm log is empty and I've been online for 2 hours. My router stops the majority of the nasties.

[dmcconnell]

From the router security log:

<<
Fri, 2006-02-24 00:34:22 - TCP Packet - Source:201.50.151.142,2778 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:23 - TCP Packet - Source:81.38.21.139,3396 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:23 - TCP Packet - Source:196.203.63.80,50044 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:23 - TCP Packet - Source:196.203.63.80,50044 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:23 - TCP Packet - Source:85.176.99.84,47534 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:23 - TCP Packet - Source:85.176.99.84,47534 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:23 - TCP Packet - Source:84.100.169.228,4372 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:23 - TCP Packet - Source:84.100.169.228,4372 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:24 - TCP Packet - Source:195.234.63.15,1262 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:24 - TCP Packet - Source:83.198.130.245,3947 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:24 - TCP Packet - Source:83.198.130.245,3947 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:24 - TCP Packet - Source:217.216.59.160,3675 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:24 - TCP Packet - Source:217.216.59.160,3675 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:24 - TCP Packet - Source:84.174.91.81,63835 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:24 - TCP Packet - Source:84.174.91.81,63835 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:26 - TCP Packet - Source:84.222.196.243,3995 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:26 - TCP Packet - Source:172.181.129.47,1405 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:26 - TCP Packet - Source:81.38.74.88,3231 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:26 - TCP Packet - Source:81.38.74.88,3231 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:26 - TCP Packet - Source:84.100.169.228,4372 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:26 - TCP Packet - Source:84.100.169.228,4372 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:26 - TCP Packet - Source:84.160.121.214,2555 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:85.98.210.47,2030 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:85.98.210.47,2030 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:83.156.153.109,4788 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:83.156.153.109,4788 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:86.198.201.66,1635 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:86.198.201.66,1635 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:217.216.59.171,4265 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:27 - TCP Packet - Source:217.216.59.171,4265 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:28 - TCP Packet - Source:84.4.111.117,33933 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:28 - TCP Packet - Source:201.50.151.142,2778 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:28 - TCP Packet - Source:201.50.151.142,2778 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:29 - TCP Packet - Source:81.38.21.139,3396 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:29 - TCP Packet - Source:85.176.99.84,47534 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:29 - TCP Packet - Source:84.160.121.214,2555 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:29 - TCP Packet - Source:84.160.121.214,2555 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:30 - TCP Packet - Source:195.234.63.15,1262 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:30 - TCP Packet - Source:195.234.63.15,1262 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:30 - TCP Packet - Source:196.203.63.80,50044 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:30 - TCP Packet - Source:196.203.63.80,50044 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:30 - TCP Packet - Source:85.98.210.47,2030 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:30 - TCP Packet - Source:85.98.210.47,2030 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:30 - TCP Packet - Source:84.174.91.81,63835 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:31 - TCP Packet - Source:84.4.111.117,33933 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:31 - TCP Packet - Source:84.4.111.117,33933 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:32 - TCP Packet - Source:86.68.42.113,1373 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:32 - TCP Packet - Source:84.100.169.228,4372 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:32 - TCP Packet - Source:84.100.169.228,4372 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:33 - TCP Packet - Source:84.168.236.99,1870 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:34 - TCP Packet - Source:213.46.123.221,2222 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:35 - TCP Packet - Source:86.68.42.113,1373 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:35 - TCP Packet - Source:85.98.210.47,2030 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:36 - TCP Packet - Source:213.39.157.59,4163 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:36 - TCP Packet - Source:213.39.157.59,4163 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:36 - TCP Packet - Source:201.37.74.104,4001 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:36 - TCP Packet - Source:201.37.74.104,4001 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:36 - TCP Packet - Source:84.168.236.99,1870 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:36 - TCP Packet - Source:84.168.236.99,1870 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:37 - TCP Packet - Source:84.4.111.117,33933 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:37 - TCP Packet - Source:213.46.123.221,2222 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:37 - TCP Packet - Source:213.46.123.221,2222 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:37 - TCP Packet - Source:87.2.99.185,3668 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:37 - TCP Packet - Source:87.2.99.185,3668 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:39 - TCP Packet - Source:213.39.157.59,4163 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:39 - TCP Packet - Source:201.37.74.104,4001 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:39 - TCP Packet - Source:81.173.183.38,2128 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:40 - TCP Packet - Source:87.2.99.185,3668 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:40 - TCP Packet - Source:87.2.99.185,3668 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:41 - TCP Packet - Source:84.168.211.143,4227 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:41 - TCP Packet - Source:86.68.42.113,1373 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:41 - TCP Packet - Source:86.68.42.113,1373 Destination:192.168.0.2,9090 - [DOS]
Fri, 2006-02-24 00:34:42 - TCP Packet - Source:84.168.236.99,1870 Destination:192.168.0.2,9090 - [eMule1 match]
Fri, 2006-02-24 00:34:42 - TCP Packet - Source:81.173.183.38,2128 Destination:192.168.0.2,9090 - [eMule1 match]

[Cavalier90]

From what you can see the firewall seems to be allowing access. The error suggests sharing problems and I'm afraid I've reached the end of my knowledge as beyond here I've usually managed to gain access. Hopefully one of the other network guys will be able to pick up from here. Sorry.

I'll do some more digging and may get back to you if I find anything.

[dmcconnell]

Thanks for your help - I can at least access the laptop which I couldn't previously.

Much appreciated.

[dmcconnell]

I managed to view the desktop shared documents once, before it disappeared again!

[Cavalier90]

Have you installed ZoneAlarm on the laptop? If not do so and add the ip address of the desktop as you did before. At least then both machines are configured the same and we can rule some things out.

[dmcconnell]

I was downloading SP2 to get both systems up to the same level, then will add zonealarm to that as well. Am doing it now.

Have installed and upgraded to zonealarm pro on both machines now.

[Cavalier90]

Has it made any difference to accessing each machine from the other?

[dmcconnell]

None whatsoever.
Except that after getting zonealarm pro, it was stopping outlook from accessing my mail server totally. So have removed it.

The desktop now has its internet connection from an "unknown internert sharing device" and wont let me do anything with it (internet gateway icon).
Still no joy at accessing the desktop from the laptop, but have full access to the laptop from the desktop.

[Variable]

Windows XP Pro uses a Local Security database to authenticate access to network shares. If you can see the shars but cannot access them that is becuase the username and password you used to log intot he machine you are using to connect to a shared folder is not valid for the the computer that you are connecting to.

There are two ways to go with networking between home pc's secure and not secure. Since you are using Emule I will assume that security is not an issue and NTFS permissions may be beyond what you would like to get in to, either way, here is a link explaining how to do it.

http://www.practicallynetworked.com/sharing/xp_filesharing/

[Cavalier90]

Useful pointer Variable. I've added it to my Bookmarks.

I hope dmmconnell will make use of it.

Thanks.

[dmcconnell]

Many thanks for your help, both of you.

Will have a read of the link and hope to get things sorted out.

Why is the emule such a security hazard, and what potential implications could it incur?

[dmcconnell]

Sorry to be a pain, but I don't understand exactly what I am to follow on that link.

Both the the PCs have simple file sharing enabled.
I don't enter a password, etc, to log onto either. When I installed Windows I left the box blank - it does pop up every so often asking for it to be changed and I click OK and it says its changed.

Still in teh dark I'm afraid...

[Cavalier90]

From what I read of eMule it is a peer to peer package for sharing files. The trouble is a peer to peer sharing package allows anyone access through your firewalls. Depending on the software it may or may not be very secure. The company I work for uses peer to peer to transfer financial information, but the security that is built in is intense. Most file sharing by P2P has virtually no security; you allow anyone and everyone access to your computer.

As for accessing each machine, I read the article and it seemed to be saying simple file sharing should work. If each machine has simple file sharing enabled, there should be no problem, unless the actual folder you want to share is not enabled. Check the folder by using My Computer and select the folder using the right button and check the Sharing and Security setting.

[dmcconnell]

Hmmmm - well I disabled simple file sharing, and disabled the security option in policies.

Now I can see the drives on the desktop. All the computers have disappeared from the workgroup though.
When I try to access the contents of the drives, sometimes I get the permissions error, but now the wireless link constantly resets and I lose the connection. Now its doing it even when I'm not trying to view the other machine

[dmcconnell]

Thats what I got from it when I read it - simple file sharing should work.
I'm not trying to share folders, I've enabled sharing for the 3 disk drives and 2 dvd roms on the desktop.
Lots of the options that are shown on that link aren't there on mine.

With regards to emule, I have limited the sharing to the incoming folder only. Thought that meant my whole ppc isn't seen by others and only files Ive downloaded are available to share?

[dmcconnell]

Success! Have now successfully opened a pdf on the laptop from teh desktop, and have added a printer that is connected to teh desktop.

Very suprised that this has worked - was almost despairing!

Cavalier and variable - thank you so much for taking the time and trouble to help sort this out. You are true gentlemen and scholars!

All the best.

[Cavalier90]

Let's see if Variable can come up with any further suggestions.

[Cavalier90]

Congrats, glad to help in a small way.

[dmcconnell]

And its printing!

Don't be modest - you were a great help!! I'd have pulled my hair out ages ago if you hadn't been suggesting things.