Server 2000 + file sharing + connection issues

[Steven Burn]

Overview:

Having never worked with routers or networking before I have to admit I am more than a little perplexed by this.

The short version is, my brother got a router so he could use my broadband connection via Windows 2000 Server (fully patched). Whilst all machines can connect to the internet, the Server 2000 machine is experiencing frequent connection problems (e-mail via OE comes back with socket errors, webpages return DNS errors or "Action Cancelled"). The XP machines have no problems whatsoever with the internet.

With respect to file sharing, I've got shares setup on all 3 systems.

Machine 1 (Windows Server 2000):

Can see both machines, but cannot access them. Ping returns timeout, attempts to connect via any protocol return either network path, DNS or etc etc.... errors. Attempts to connect to one of the XP machines via UNC returns requests for confirmation from the XP machine (permission), once permission is given, a network path error is returned (disabling permission request does not correct this).

In addition, incoming connections via the internet are working just fine. Whatever this problem is, it is restricted to internal machines only.

Machine 2 (XP Pro SP1):

Can see the Windows 2000 shares just fine and has no problem accessing them, but cannot access Machine 3's shares (returns network path error).

Machine 3 (XP Pro SP1) (my brothers system)

Cannot see either of the other two systems (ping works and attempts to connect to the 2000 Server IP via HTTP and FTP work without any problems, but attempts to connect via UNC return "Invalid network path" errors).

********************************************
Network Setup
********************************************

Netgear ADSL Firewall Router DG384G

Machine 1:

Windows Server 2000 (fully patched)
Setup as DC with Active Directory (runs DNS, IIS, FTP and SMTP server's)*
Connected to router via RJ45

* Never had a problem with any of these until the routers installation. Router is also configured to allow incoming and outgoing connections to the required ports and has DNS set to my ISP's DNS servers (turning off internal DNS server prevents my 2KS machine connecting to itself???).

Machine 2:

Windows XP Pro SP1
Connected to router via RJ45

Machine 3:

Windows XP Pro SP1
Wireless connection to router

I've tried disabling the software firewall (Tiny Personal Firewall on all 3 machines) but this makes no difference.

Should any further information be required, I'll be happy to supply it. Otherwise, any advice/suggestions would be more than appreciated (spent 3 days trying to sort this out already and it's doing my head in).

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Steven Burn]

Well, I somehow managed to get the 3 machines to see each other and file sharing is now working )

Only two things left to sort out;

1. The 2K Server connection problems
2. Why "Map network drive" does not show on the XP machines (even after a registry tweak) (had to do a reg tweak for the 2K machine but thankfully, that one worked).

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

Overview:

Having never worked with routers or networking before I have to admit I am more than a little perplexed by this.

The short version is, my brother got a router so he could use my broadband connection via Windows 2000 Server (fully patched). Whilst all machines can connect to the internet, the Server 2000 machine is experiencing frequent connection problems (e-mail via OE comes back with socket errors, webpages return DNS errors or "Action Cancelled"). The XP machines have no problems whatsoever with the internet.

With respect to file sharing, I've got shares setup on all 3 systems.

Machine 1 (Windows Server 2000):

Can see both machines, but cannot access them. Ping returns timeout, attempts to connect via any protocol return either network path, DNS or etc etc.... errors. Attempts to connect to one of the XP machines via UNC returns requests for confirmation from the XP machine (permission), once permission is given, a network path error is returned (disabling permission request does not correct this).

In addition, incoming connections via the internet are working just fine. Whatever this problem is, it is restricted to internal machines only.

Machine 2 (XP Pro SP1):

Can see the Windows 2000 shares just fine and has no problem accessing them, but cannot access Machine 3's shares (returns network path error).

Machine 3 (XP Pro SP1) (my brothers system)

Cannot see either of the other two systems (ping works and attempts to connect to the 2000 Server IP via HTTP and FTP work without any problems, but attempts to connect via UNC return "Invalid network path" errors).

********************************************
Network Setup
********************************************

Netgear ADSL Firewall Router DG384G

Machine 1:

Windows Server 2000 (fully patched)
Setup as DC with Active Directory (runs DNS, IIS, FTP and SMTP server's)*
Connected to router via RJ45

* Never had a problem with any of these until the routers installation. Router is also configured to allow incoming and outgoing connections to the required ports and has DNS set to my ISP's DNS servers (turning off internal DNS server prevents my 2KS machine connecting to itself???).

Machine 2:

Windows XP Pro SP1
Connected to router via RJ45

Machine 3:

Windows XP Pro SP1
Wireless connection to router

I've tried disabling the software firewall (Tiny Personal Firewall on all 3 machines) but this makes no difference.

Should any further information be required, I'll be happy to supply it. Otherwise, any advice/suggestions would be more than appreciated (spent 3 days trying to sort this out already and it's doing my head in).

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Tony]

Are you running a workgroup or domain?


Overview:

Having never worked with routers or networking before I have to admit I am
more than a little perplexed by this.

The short version is, my brother got a router so he could use my broadband
connection via Windows 2000 Server (fully patched). Whilst all machines can
connect to the internet, the Server 2000 machine is experiencing frequent
connection problems (e-mail via OE comes back with socket errors, webpages
return DNS errors or "Action Cancelled"). The XP machines have no problems
whatsoever with the internet.

With respect to file sharing, I've got shares setup on all 3 systems.

Machine 1 (Windows Server 2000):

Can see both machines, but cannot access them. Ping returns timeout,
attempts to connect via any protocol return either network path, DNS or etc
etc.... errors. Attempts to connect to one of the XP machines via UNC
returns requests for confirmation from the XP machine (permission), once
permission is given, a network path error is returned (disabling permission
request does not correct this).

In addition, incoming connections via the internet are working just fine.
Whatever this problem is, it is restricted to internal machines only.

Machine 2 (XP Pro SP1):

Can see the Windows 2000 shares just fine and has no problem accessing them,
but cannot access Machine 3's shares (returns network path error).

Machine 3 (XP Pro SP1) (my brothers system)

Cannot see either of the other two systems (ping works and attempts to
connect to the 2000 Server IP via HTTP and FTP work without any problems,
but attempts to connect via UNC return "Invalid network path" errors).

********************************************
Network Setup
********************************************

Netgear ADSL Firewall Router DG384G

Machine 1:

Windows Server 2000 (fully patched)
Setup as DC with Active Directory (runs DNS, IIS, FTP and SMTP server's)*
Connected to router via RJ45

* Never had a problem with any of these until the routers installation.
Router is also configured to allow incoming and outgoing connections to the
required ports and has DNS set to my ISP's DNS servers (turning off internal
DNS server prevents my 2KS machine connecting to itself???).

Machine 2:

Windows XP Pro SP1
Connected to router via RJ45

Machine 3:

Windows XP Pro SP1
Wireless connection to router

I've tried disabling the software firewall (Tiny Personal Firewall on all 3
machines) but this makes no difference.

Should any further information be required, I'll be happy to supply it.
Otherwise, any advice/suggestions would be more than appreciated (spent 3
days trying to sort this out already and it's doing my head in).

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Steven Burn]

domain

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Tony]

Having never worked with networking and routers, i'd say you're doing quite
well so far . Anyway, this definately sounds like a router issue. Triple
check your router config. This is usually the culprit, although with most
modern routers, you shouldn't have to setup port forwarding for your LAN.
Double check that the xp machine's built-in firewalls are not causing the
problem as well. Ensure your 2000 DC is not setup as a root dns server. If
it is, delete it and recreate the forward lookup zone. Ensure that you do
have host (A) records for all machines within your domain looup zone,
including the DC. Could be a name resolution problem. I'm assuming youve
checked the physical mediums already.



Overview:

Having never worked with routers or networking before I have to admit I am
more than a little perplexed by this.

The short version is, my brother got a router so he could use my broadband
connection via Windows 2000 Server (fully patched). Whilst all machines can
connect to the internet, the Server 2000 machine is experiencing frequent
connection problems (e-mail via OE comes back with socket errors, webpages
return DNS errors or "Action Cancelled"). The XP machines have no problems
whatsoever with the internet.

With respect to file sharing, I've got shares setup on all 3 systems.

Machine 1 (Windows Server 2000):

Can see both machines, but cannot access them. Ping returns timeout,
attempts to connect via any protocol return either network path, DNS or etc
etc.... errors. Attempts to connect to one of the XP machines via UNC
returns requests for confirmation from the XP machine (permission), once
permission is given, a network path error is returned (disabling permission
request does not correct this).

In addition, incoming connections via the internet are working just fine.
Whatever this problem is, it is restricted to internal machines only.

Machine 2 (XP Pro SP1):

Can see the Windows 2000 shares just fine and has no problem accessing them,
but cannot access Machine 3's shares (returns network path error).

Machine 3 (XP Pro SP1) (my brothers system)

Cannot see either of the other two systems (ping works and attempts to
connect to the 2000 Server IP via HTTP and FTP work without any problems,
but attempts to connect via UNC return "Invalid network path" errors).

********************************************
Network Setup
********************************************

Netgear ADSL Firewall Router DG384G

Machine 1:

Windows Server 2000 (fully patched)
Setup as DC with Active Directory (runs DNS, IIS, FTP and SMTP server's)*
Connected to router via RJ45

* Never had a problem with any of these until the routers installation.
Router is also configured to allow incoming and outgoing connections to the
required ports and has DNS set to my ISP's DNS servers (turning off internal
DNS server prevents my 2KS machine connecting to itself???).

Machine 2:

Windows XP Pro SP1
Connected to router via RJ45

Machine 3:

Windows XP Pro SP1
Wireless connection to router

I've tried disabling the software firewall (Tiny Personal Firewall on all 3
machines) but this makes no difference.

Should any further information be required, I'll be happy to supply it.
Otherwise, any advice/suggestions would be more than appreciated (spent 3
days trying to sort this out already and it's doing my head in).

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

 

[Steven Burn]

I've actually already sorted out the internal problems. The only problem that exists now is the 2K machine having problems with connections to external resources (e.g. POP, internet). Connections frequently fail and take several re-tries before they are successful (other machines don't have this problem... just the 2K machine).

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!