can't connect
Mike Lewis
out. Those that try to connect to me have a status "waiting for incoming
connection" and then time out. It takes a long time to get a 2ndary network
connection. Nothing has changed on my pc or my router.
Any suggestions:-(
--
Mike Lewis
Chartered Accountant
www.mikelewis.co.uk
Regnad Kcin
"Mike Lewis" <mike-a...@nospam.mikelewis.co.uk> wrote in message
news:jjUpb.2755$382....@newsfep4-winn.server.ntli.net...
Mike Lewis
news:Z%9qb.62373$ri.10...@twister.nyc.rr.com...
> A block at your ISP perhaps?
Possibly. I have now tried different ports and it's the same. I see from
some other messages that I am not alone.
Mike Lewis
> news:Z%9qb.62373$ri.10...@twister.nyc.rr.com...
> > A block at your ISP perhaps?
I doubt it's a block. I can search, q up, and sometimes dl a bit. I got
quite a fast dl this morning. But mostly they don't connect when started.
All of the people trying to dl from me fail to connect.
--
Mike Lewis
fred-bloggs
If you are using dhcp on your PC check your IP address is the same as
specified in your router's port forwarding rules.
--
fred
Mike Lewis
> If you are using dhcp on your PC check your IP address is the same as
> specified in your router's port forwarding rules.
I am using dhcp on my pc and the ip addresses are the same:-( The router I
have, D-Link DI-711, doesn't have much in the way of configerable port
rules. I can specify open ports by type but not port number so eg I can open
the firewall for TCP ports, or Telnet ports or similar or open it for all
ports which I am not mad keen on doing.
The symptoms are changing. Now I can get some up and down loads. Nothing has
changed in my settings. However I now notice that I am not staying connected
very long. It's as though there is hardly anybody to connect to.
I've also noticed a lot of other posts from people having problems.
--
Mike Lewis
Billy Joe
fred-bloggs,
A good suggestion though DHCP would have no bearing unless the
router were handling more than one PC or the router were for
some ungodly reason assigning random IP numbers to the only PC
connected? ;-)
If Mike has a LAN running, then static IP assignment is
recommended, though not absolutely required, so that the router
keeps the right port assignments with the right PC.
I use dynamic addressing in my 3 PC LAN and usually run MX only
on one PC (although on occasion two PCs). Typically, one
machine runs here 24/7, so it's IP remains the same from the
router, 192.168.1.100. The others are assigned 101 and 102 in
the order they are turned on (which is also reasonably constant,
as one is a portable). Unexpected things happen though, and
every once in a while the main machine will come up second, if
rebooting while two are running. It's easy to notice and simple
to fix by calling up the router admin page and switching port
numbers between the machines. No reboot nor restart of MX is
necessary.
I don't have any reason for operating this way except extreme
laziness;-0)
BJ
fred-bloggs
The manual for your router is available from
ftp://ftp.dlink.com/Gateway/di711/Manual/DI711_MANUAL_031401.zip
ftp://ftp.dlink.com/Gateway/di711b/Manual/di711revb1_manual_031401.pdf
As you pointed out, the only way to expose your PC is to allow ALL, thereby
putting your PC in a dmz. I understand why you wouldn't want to do that.
While browsing http://www.dlink.ca I came across this>
Strange router behavior: Read this information
The problems you may experience with any D-Link or Non D-Link router:
- the router seems to reboot consistently
- the router takes a lot of time to respond
- Internet transfer rates are down
- (wireless routers only) consistent wireless disconnections
Possible source of the problem:
Since the W32.Blaster Worm, many other variations of this worm have been
found. Some of them are W32/Lovsan.worm and W32/Nachi.worm. These worms
create a lot of ICMP traffic which in exchange overload the router to
eventually prevent it from communicating. Whether it's the CPU or another
component of the router that causes the failure, the problem can only be
solved through the removal of this virus.
There's a tool provided by McAfee called Stinger. This tool will detect and
remove the viruses that cause these problems. Please take a minute to read
about this tools and it's usage. You will need to run this tool on every
single computer.
Precautions to take when using the tool:
The tool will wipe out unwanted worms/viruses, but because of the method of
infection used by these worms/viruses is using the network combined with
the RPC call vulnerability, we recommend you do as follow: - Download the
stinger tool and copy it to all computers. Because the stinger does not
spread through the copy of files, you can copy this file on a disk and
bring it to other computers:
- Detach all computers from the network (This will prevent being infected
again)
- Once the process completed, connect the computer(s) to the router.
- All Windows 2000/XP should be updated with the latest Microsoft updates.
The updates fix the RPC call vulnerability
Click this link to be directed to the Stinger tool page
http://vil.nai.com/vil/stinger/
--
fred
Mike Lewis
--
Mike Lewis
"Billy Joe" <check_...@this.is.invalid> wrote in message
news:w2yqb.2747$gn1.5...@news1.news.adelphia.net...
This machine is fixed ip to the router.
Billy Joe
<snip>
> This machine is fixed ip to the router.
Sorry for drifting off earlier Mike.
When connected as a secondary you get firewall permissions
because you make an unblocked, outbound TCP connection to a
primary.
When a queued position, either your download or an uploader's,
reaches the top, the primary determines which of two TCP methods
to use based only on the settings of the source. If the
source's MX is using ports, the primary will direct the
downloader's MX to establish a normal connection using the TCP
port specified by the source. If the source is not using ports
(Unable to accept ...) then the primary will direct the source
to connect to the downloader using the downloader's specified
TCP port. If neither is using ports, an error of "Both sides
firewalled" is posted.
OK, all that said: MX does not verify that the port specified
in either MX setting is actually enabled thru the firewalls
(ISP, routers, software firewalls, et al.). Thus, if the
complete IP address, xxx.xxx.xxx.xxx:port, does not create a
path to the MX application, no upload occurs and the status is
"Time out."
So the question is: where in the path is the TCP port number
blocked or different than specified?
Preflight Check list:
First, are you running a software firewall (Win XP or other).
Some require specific port permission, while others take a more
general application approval approach.
Second, if you have a router, does the port forwarding table
match the IP address of the machine running MX and is the port
number the same as specified in MX.
Third, there is always the possibility your ISP has decided to
restrict known p2p ports. While I question their rights to do
so, I'd not suggest taking them to court over it;-0) One way to
avert this is to run your secondary connection in passive mode,
i.e. TCP setting "Unable to accept ..."
Fourth, if you are running on an institutional LAN then your
school or business has probably decided to take action against
this sort of usage and you probably can not, and should not, get
around the block.
Note: if the third suggestion works, then you will not be able
to download from any sources running in the same mode.
I hope some of this may be of help,
BJ
Mike Lewis
> http://vil.nai.com/vil/stinger/
Shit. There was one. sdbot.worm.gen. Gone now.
--
Mike Lewis
Pamela and Howard Signa
"Mike Lewis" <mike-a...@nospam.mikelewis.co.uk> wrote in message
news:jjUpb.2755$382....@newsfep4-winn.server.ntli.net...