Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > NZ Computing > Windows Networking

Reply
Thread Tools

Windows Networking

 
 
Craig Shore
Guest
Posts: n/a
 
      05-17-2004
On Mon, 17 May 2004 19:08:40 +1200, "Mr Scebe" <(E-Mail Removed)> wrote:

>
>"Craig Shore" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>
>> XP's firewall isn't on, and Sygate Personal Firewall has the Network
>> Neighbourhood completley enabled.

>
>Try to connect to a network resource using the IP address of the other PC
>ie: net use \\192.168.0.1\share


This machine (the one with the problem) is 192.168.1.2.
The ADSL router is 192.168.1.1
The other computer (laptop) is 192.168.1.3


C:\Documents and Settings\user>net use \\192.168.1.3\share
System error 53 has occurred.

The network path was not found.


C:\Documents and Settings\user>

>This will determine whether the problem lies within LANManager or not. You
>don't have an LMHosts file with out of date data?


Don't know. I tried unticking the Enable LMHOSTS Lookup checkbox just now but
no joy.

>Also at the command prompt, type netstat -na which will show you what ports
>your PC is listening on.
>
>Report your findings, and we can diagnose it further from there.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\user>netstat -na

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1097 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1403 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8010 0.0.0.0:0 LISTENING
TCP 192.168.1.2:139 0.0.0.0:0 LISTENING
TCP 192.168.1.2:1097 205.188.12.4:5190 ESTABLISHED
TCP 192.168.1.2:1403 202.20.93.13:119 ESTABLISHED
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:1027 *:*
UDP 0.0.0.0:1033 *:*
UDP 0.0.0.0:1043 *:*
UDP 0.0.0.0:1207 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1037 *:*
UDP 127.0.0.1:1040 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.2:123 *:*
UDP 192.168.1.2:137 *:*
UDP 192.168.1.2:138 *:*
UDP 192.168.1.2:1900 *:*

C:\Documents and Settings\user>


 
Reply With Quote
 
 
 
 
Mr Scebe
Guest
Posts: n/a
 
      05-17-2004

"Craig Shore" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Mon, 17 May 2004 19:08:40 +1200, "Mr Scebe" <(E-Mail Removed)>

wrote:
>
> >
> >"Craig Shore" <(E-Mail Removed)> wrote in message
> >news:(E-Mail Removed).. .
> >
> >> XP's firewall isn't on, and Sygate Personal Firewall has the Network
> >> Neighbourhood completley enabled.

> >
> >Try to connect to a network resource using the IP address of the other PC
> >ie: net use \\192.168.0.1\share

>
> This machine (the one with the problem) is 192.168.1.2.
> The ADSL router is 192.168.1.1
> The other computer (laptop) is 192.168.1.3
>
>
> C:\Documents and Settings\user>net use \\192.168.1.3\share
> System error 53 has occurred.


Sorry, maybe i wasn't clear. You need to put \\192.168.1.3\<share> where
<share> is the name of the resource you would normally connect to (ie: c$ or
users or whatever)

The rest of it seems ok, but you have some strange ports open. Make sure
your firewall is functioning properly because 80, 139 and 445 are all
exploitable from outside.

Also type net view and nbtstat -n on the command line. This will give you
more info to help resolve.

Let us know how you get on.

--
Mr Scebe
"Never trust a woman or a government"
~Yellowbeard


 
Reply With Quote
 
 
 
 
Craig Shore
Guest
Posts: n/a
 
      05-17-2004
On Mon, 17 May 2004 22:15:43 +1200, "Mr Scebe" <(E-Mail Removed)>
wrote:

>Let us know how you get on.


Got it sorted I think. It was the dumb user that was the cause

In the firewall I have all the MS stuff that tries to access the net
blocked. That includes NDIS User Mode I/O Driver.
I guess when you tell the firewall to enanble the network
neighbourhood it allows the necessary ports to operate in NDIS even
though it's blocked. What happened was when I updated Windows it
updated NDIS. The firewall keeps an eye on all dll's and apps, and if
any change it alerts you and asks for authority to allow the traffic
through. I thought that one was blocked anyway, why was it asking me
and pressed No. It must have been asking because it had changed and
some of it is allowed access because of the Network Neighbourhood
being enabled.


 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Internet networking , group networking,business leads,new business opportunities,like having many sales peoples elie Computer Support 0 08-18-2007 10:12 AM
networking two pc together with wireless networking ? Andy Wireless Networking 4 02-26-2007 06:02 PM
PROBLEMS WITH NETWORKING - NEW TO NETWORKING =?Utf-8?B?QUJTUE9QVVA=?= Wireless Networking 2 03-23-2005 08:31 AM
[Reminder] Online chat with Networking & Devices VP about Networking in Longhorn Eddy Malik [MSFT] Wireless Networking 0 03-22-2005 03:27 AM
networking 2 pc with a networking hub and 1 internet connection barry crowley Computer Support 20 02-27-2004 05:09 AM



Advertisments