Thread View: comp.os.ms-windows.networking.ras
7 messages
7 total messages
Started by Steve
Thu, 17 Apr 1997 00:00
Can't ping outside the RAS machine
Author: Steve
Date: Thu, 17 Apr 1997 00:00
Date: Thu, 17 Apr 1997 00:00
29 lines
1944 bytes
1944 bytes
Ever since our RAS (NT3.51 sp5) crashed horribly a few weeks ago and needed a complete re-installation we have been unable to get it to work properly with IP. All other aspects are ok ie. IPX etc, I can perform a netware login so no worries there. I shall try to describe what we have done here: After we initially failed to get RAS working we re-reinstalled and assigned ONE IP address to the NIC and set up RAS, dialled in and everything worked properly. We then added more IP addresses (via regedt32 because there are quite a few) to the NIC (as this machine is our mail, DNS, FTP and RAS server). This is where the IP fell over, RAS clients can still dial in, be assigned an IP address and ping the local machine but can't ping anything externally ie. outside the NIC, including IPs on our own subnet. I have tried fiddling with various settings such as enable IP routing, adding a DisableOtherSrcPackets registry key, changing the wallpaper and standing on one leg but to no avail. If anyone has any suggestions, especially ones which cause our NT RAS to start working properly then I will be forever indebted to you. Should any extra info be required please don't hesitate to ask, eg. routing table dump, etc. TIA Steve Martin - Sequence Collective
Re: Can't ping outside the RAS machine
Author: Steve Martin
Date: Thu, 17 Apr 1997 00:00
Date: Thu, 17 Apr 1997 00:00
26 lines
1544 bytes
1544 bytes
Yup, it is set Andy Smallwood <asmallwood@logicline.com> wrote in article <01bc4b4a$544c7050$22b8cbc2@doreen>... > The one obvious thing you don't mention is whether the 'Allow remote TCP/IP > clients to access' is set to 'Entire network' or 'This computer only' in > your RAS Server TCP/IP configuration. > Go Control Panel->Network->Services->Remote Access > Service->Properties->Network->TCP/IP configure to check. > > Andy > > Steve <smartin~@~jumo.com> wrote in article > <01bc4b28$719f94b0$cc639fc2@betelgeux>... > > > > Ever since our RAS (NT3.51 sp5) crashed horribly a few weeks ago and > needed > > a complete re-installation we have been unable to get it to work properly > > with IP. All other aspects are ok ie. IPX etc, I can perform a netware > > login so no worries there. > >
Re: Can't ping outside the RAS machine
Author: Michael Bormann
Date: Thu, 17 Apr 1997 00:00
Date: Thu, 17 Apr 1997 00:00
43 lines
2093 bytes
2093 bytes
In TCP Options on setting IP, there is an option to set on "Forwarding IP", this must be set, otherwise it will never route forward. if you can't find it there, open regedit, goto localmachine\currentcontrolset\system\tcpip\parameters" and set ForwardBroadcasts and IPEnableRouter to a value of 1 then it should work -- Good luck Michael_Bormann@t-online.de Steve Martin <steve@~sequence.co.uk> schrieb im Beitrag <01bc4b62$9f1409a0$cc639fc2@STEVE.JUMO.COM>... > > Yup, it is set > > Andy Smallwood <asmallwood@logicline.com> wrote in article > <01bc4b4a$544c7050$22b8cbc2@doreen>... > > The one obvious thing you don't mention is whether the 'Allow remote > TCP/IP > > clients to access' is set to 'Entire network' or 'This computer only' in > > your RAS Server TCP/IP configuration. > > Go Control Panel->Network->Services->Remote Access > > Service->Properties->Network->TCP/IP configure to check. > > > > Andy > > > > Steve <smartin~@~jumo.com> wrote in article > > <01bc4b28$719f94b0$cc639fc2@betelgeux>... > > > > > > Ever since our RAS (NT3.51 sp5) crashed horribly a few weeks ago and > > needed > > > a complete re-installation we have been unable to get it to work > properly > > > with IP. All other aspects are ok ie. IPX etc, I can perform a netware > > > login so no worries there. > > > > > >
Re: Can't ping outside the RAS machine
Author: Andy Smallwood
Date: Thu, 17 Apr 1997 00:00
Date: Thu, 17 Apr 1997 00:00
17 lines
1321 bytes
1321 bytes
The one obvious thing you don't mention is whether the 'Allow remote TCP/IP clients to access' is set to 'Entire network' or 'This computer only' in your RAS Server TCP/IP configuration. Go Control Panel->Network->Services->Remote Access Service->Properties->Network->TCP/IP configure to check. Andy Steve <smartin~@~jumo.com> wrote in article <01bc4b28$719f94b0$cc639fc2@betelgeux>... > > Ever since our RAS (NT3.51 sp5) crashed horribly a few weeks ago and needed > a complete re-installation we have been unable to get it to work properly > with IP. All other aspects are ok ie. IPX etc, I can perform a netware > login so no worries there.
Re: Can't ping outside the RAS machine
Author: Steve Martin
Date: Thu, 17 Apr 1997 00:00
Date: Thu, 17 Apr 1997 00:00
25 lines
1583 bytes
1583 bytes
Sorry, forgot to mention, it is set to 'Entire Network' Andy Smallwood <asmallwood@logicline.com> wrote in article <01bc4b4a$544c7050$22b8cbc2@doreen>... > The one obvious thing you don't mention is whether the 'Allow remote TCP/IP > clients to access' is set to 'Entire network' or 'This computer only' in > your RAS Server TCP/IP configuration. > Go Control Panel->Network->Services->Remote Access > Service->Properties->Network->TCP/IP configure to check. > > Andy > > Steve <smartin~@~jumo.com> wrote in article > <01bc4b28$719f94b0$cc639fc2@betelgeux>... > > > > Ever since our RAS (NT3.51 sp5) crashed horribly a few weeks ago and > needed > > a complete re-installation we have been unable to get it to work properly > > with IP. All other aspects are ok ie. IPX etc, I can perform a netware > > login so no worries there. > >
Re: Can't ping outside the RAS machine
Author: Steve
Date: Fri, 18 Apr 1997 00:00
Date: Fri, 18 Apr 1997 00:00
26 lines
1896 bytes
1896 bytes
Nope, no joy. I am under the impression that the problem may have something to do with the routes set up in the route table. I read somewhere that the order in which the RAS service starts with respect to the other TCP services may have some effect on the routes. Oh, Michael, you said to change settings in: > localmachine\currentcontrolset\system\tcpip\parameters" I assumed you meant _local_machine\system\currentcontrolset\services\TCPIP\parameters as I couldn't find ForwardBroadcasts elsewhere. Is there really light at the end of the tunnel or is that just a chap with a torch. Michael Bormann <Michael_Bormann@t-online.de> wrote in article <01bc4b93$9491f380$2a0219c2@funnel41.btx.dtag.de>... > In TCP Options on setting IP, there is an option to set on "Forwarding IP", > this must be set, otherwise it will never route forward. > if you can't find it there, open regedit, goto > localmachine\currentcontrolset\system\tcpip\parameters" and set > ForwardBroadcasts and IPEnableRouter to a value of 1 > then it should work > -- > Good luck
Re: Can't ping outside the RAS machine
Author: Steve
Date: Mon, 21 Apr 1997 00:00
Date: Mon, 21 Apr 1997 00:00
31 lines
2417 bytes
2417 bytes
I Fixed it. For those of you who are interested, read on: I don't know WHY the changes I made worked simply that they DID. We previously had 15 IP addresses assigned to the NIC along with 3 assigned to RAS (2 ports + 1 for RAS itself). I had assumed that these settings were NOT to blame so I left them alone for a while. After fiddling with every setting & registry key that I could glean from this newsgroup I was left stumped. I then sat down and scratched my head for a while and realised that we were only using 4 out of the 15 NIC IPs so I removed the extraneous IPs and tried again... BINGO everything worked as it should. I then started thinking about a problem I had been getting some months before which was similar in nature in that I could ping anything outside our subnet plus the IPs assigned the the local RAS machine. This at the time didn't bother me too much as I was only really bothered about surfing from home and besides, the problem was intermittent in that some client machines could access everything and others were restricted. So I added the IP addresses back to the NIC one by one and found that: <=13 IPs - Everything OK 14IPs - Ping external & local machine, no local subnet 15+IPs - Ping only local machine Now I know HOW to get around this problem but I don't know WHY. If anyone has come across this phenomenon before or has some Idea what went wrong (M$ bug???) then I'd really appreciate it if you could mail me at steve@sequence.co.uk ps. cheers everyone for your input on this issue TIA
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads