From: Dave Tully Subject: Excessive connect time Date: 04 Nov 1996 19:16:51 -0700 This is a multi-part message in MIME format. --------------77032B877C87 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi My name is Dave Tully..just signed up tonite and I have a question for you. Let me describe what I'm trying to do and what the problem is. I am a member of TEN (Total Entertainment Network) which is a multi player gaming community. Under my "old" ISP, my connects were never good enough to play. I was hoping that your T3 internet capabilities would speed things up. With the help of the TEN tech support I have put together a batch file (see the attached TRACE.BAT) that uses tracert and ping to identify the bottlenecks. Please see the other attached file (TRACE.TXT) that the batch file creates. I'd like you to take a look at the 2nd location CISCO0.XMISSION.COM 198.60.22.1 which has approx 1454ms and as high as 2041ms. Is there something wrong? The highest I've ever seen is 600ms or so. ** please reply to: TullyD@jcave.com Appreciate your help Dave --------------77032B877C87 Content-Type: text/plain; charset=us-ascii; name="trace.bat" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="trace.bat" copy c:\trace.txt c:\trace.old del c:\trace.txt pause tracert horrorshow.ten.net >> c:\trace.txt ping -n 30 horrowshow.ten.net >> c:\trace.txt tracert dipper.ten.net >> c:\trace.txt ping -n 30 dipper.ten.net >> c:\trace.txt tracert darkride.ten.net >> c:\trace.txt ping -n 30 darkride.ten.net >> c:\trace.txt cd \ edit trace.txt --------------77032B877C87 Content-Type: text/plain; charset=us-ascii; name="Trace.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Trace.txt" Tracing route to horrorshow.ten.net [206.173.136.138] over a maximum of 30 hops: 1 160 ms 154 ms 163 ms annex2.xmission.com [198.60.22.8] 2 1454 ms 601 ms 200 ms cisco0.xmission.com [198.60.22.1] 3 179 ms 171 ms 295 ms eli-xmission.eli.net [206.29.193.17] 4 187 ms 203 ms 162 ms core1-fddi.SaltLake.eli.net [207.0.56.17] 5 734 ms 183 ms 167 ms border2-hssi2-0.Denver.mci.net [204.70.29.9] 6 176 ms 216 ms 180 ms core1-fddi-1.Denver.mci.net [204.70.3.113] 7 218 ms 229 ms 214 ms 204.70.1.154 8 238 ms * 242 ms 204.70.1.154 9 252 ms 236 ms 214 ms borderx1-fddi-1.LosAngeles.mci.net [204.70.170.52] 10 265 ms 229 ms 230 ms cuc-international.LosAngeles.mci.net [204.70.170.102] 11 253 ms 250 ms 248 ms 206.83.90.132 12 286 ms * 235 ms 206.83.90.129 13 241 ms 268 ms 271 ms horrorshow.ten.net [206.173.136.138] Trace complete. Bad IP address horrowshow.ten.net. Tracing route to dipper.ten.net [199.94.217.192] over a maximum of 30 hops: 1 169 ms 153 ms 148 ms annex2.xmission.com [198.60.22.8] 2 241 ms 291 ms 254 ms cisco0.xmission.com [198.60.22.1] 3 433 ms 587 ms 474 ms eli-xmission.eli.net [206.29.193.17] 4 381 ms 362 ms 466 ms core1-fddi.SaltLake.eli.net [207.0.56.17] 5 187 ms 187 ms 273 ms border2-hssi2-0.Denver.mci.net [204.70.29.9] 6 172 ms 168 ms 172 ms core1-fddi-1.Denver.mci.net [204.70.3.113] 7 * 387 ms 277 ms core2-hssi-3.Boston.mci.net [204.70.1.10] 8 315 ms 239 ms 246 ms core2-hssi-3.Boston.mci.net [204.70.1.10] 9 218 ms 348 ms 276 ms core.Boston.mci.net [204.70.4.137] 10 239 ms 396 ms 245 ms border1-fddi-0.Boston.mci.net [204.70.2.34] 11 250 ms 258 ms * nearnet.Boston.mci.net [204.70.20.6] 12 425 ms 359 ms 399 ms cambridge2-cr2.bbnplanet.net [192.233.33.2] 13 234 ms 240 ms 235 ms cambridge1-cr1.bbnplanet.net [192.233.149.201] 14 232 ms 223 ms 244 ms dipper.ten.net [199.94.217.192] Trace complete. Pinging dipper.ten.net [199.94.217.192] with 32 bytes of data: Reply from 199.94.217.192: bytes=32 time=252ms TTL=242 Reply from 199.94.217.192: bytes=32 time=245ms TTL=242 Reply from 199.94.217.192: bytes=32 time=259ms TTL=242 Reply from 199.94.217.192: bytes=32 time=377ms TTL=242 Reply from 199.94.217.192: bytes=32 time=238ms TTL=242 Reply from 199.94.217.192: bytes=32 time=239ms TTL=242 Reply from 199.94.217.192: bytes=32 time=219ms TTL=242 Reply from 199.94.217.192: bytes=32 time=236ms TTL=242 Reply from 199.94.217.192: bytes=32 time=229ms TTL=242 Reply from 199.94.217.192: bytes=32 time=229ms TTL=242 Reply from 199.94.217.192: bytes=32 time=248ms TTL=242 Reply from 199.94.217.192: bytes=32 time=215ms TTL=242 Reply from 199.94.217.192: bytes=32 time=225ms TTL=242 Reply from 199.94.217.192: bytes=32 time=243ms TTL=242 Reply from 199.94.217.192: bytes=32 time=215ms TTL=242 Reply from 199.94.217.192: bytes=32 time=226ms TTL=242 Reply from 199.94.217.192: bytes=32 time=231ms TTL=242 Reply from 199.94.217.192: bytes=32 time=264ms TTL=242 Request timed out. Request timed out. Reply from 199.94.217.192: bytes=32 time=220ms TTL=242 Request timed out. Reply from 199.94.217.192: bytes=32 time=257ms TTL=242 Reply from 199.94.217.192: bytes=32 time=280ms TTL=242 Reply from 199.94.217.192: bytes=32 time=237ms TTL=242 Request timed out. Reply from 199.94.217.192: bytes=32 time=247ms TTL=242 Reply from 199.94.217.192: bytes=32 time=232ms TTL=242 Reply from 199.94.217.192: bytes=32 time=206ms TTL=242 Reply from 199.94.217.192: bytes=32 time=214ms TTL=242 Tracing route to darkride.ten.net [204.162.251.33] over a maximum of 30 hops: 1 165 ms 156 ms 170 ms annex2.xmission.com [198.60.22.8] 2 2041 ms 284 ms 183 ms cisco0.xmission.com [198.60.22.1] 3 361 ms 383 ms 408 ms eli-xmission.eli.net [206.29.193.17] 4 189 ms 213 ms 166 ms core1-fddi.SaltLake.eli.net [207.0.56.17] 5 193 ms 187 ms 198 ms border2-hssi2-0.Denver.mci.net [204.70.29.9] 6 186 ms * 194 ms core1-fddi-1.Denver.mci.net [204.70.3.113] 7 233 ms 252 ms 216 ms barrnet.SanFrancisco.mci.net [166.48.19.250] 8 237 ms 217 ms 215 ms barrnet.SanFrancisco.mci.net [166.48.19.250] 9 264 ms 256 ms 272 ms paloalto-cr4.bbnplanet.net [131.119.0.204] 10 * 487 ms 349 ms tenet2.bbnplanet.net [131.119.26.22] 11 * 239 ms 260 ms darkride.ten.net [204.162.251.33] Trace complete. Pinging darkride.ten.net [204.162.251.33] with 32 bytes of data: Reply from 204.162.251.33: bytes=32 time=243ms TTL=245 Reply from 204.162.251.33: bytes=32 time=232ms TTL=245 Reply from 204.162.251.33: bytes=32 time=231ms TTL=245 Reply from 204.162.251.33: bytes=32 time=248ms TTL=245 Reply from 204.162.251.33: bytes=32 time=243ms TTL=245 Reply from 204.162.251.33: bytes=32 time=238ms TTL=245 Reply from 204.162.251.33: bytes=32 time=243ms TTL=245 Request timed out. Request timed out. Request timed out. Reply from 204.162.251.33: bytes=32 time=235ms TTL=245 Reply from 204.162.251.33: bytes=32 time=241ms TTL=245 Request timed out. Reply from 204.162.251.33: bytes=32 time=229ms TTL=245 Request timed out. Reply from 204.162.251.33: bytes=32 time=231ms TTL=245 Reply from 204.162.251.33: bytes=32 time=289ms TTL=245 Reply from 204.162.251.33: bytes=32 time=227ms TTL=245 Reply from 204.162.251.33: bytes=32 time=235ms TTL=245 Reply from 204.162.251.33: bytes=32 time=212ms TTL=245 Reply from 204.162.251.33: bytes=32 time=247ms TTL=245 Request timed out. Reply from 204.162.251.33: bytes=32 time=221ms TTL=245 Reply from 204.162.251.33: bytes=32 time=268ms TTL=245 Request timed out. Reply from 204.162.251.33: bytes=32 time=249ms TTL=245 Request timed out. Reply from 204.162.251.33: bytes=32 time=220ms TTL=245 Reply from 204.162.251.33: bytes=32 time=218ms TTL=245 Request timed out. --------------77032B877C87-- ------------------------------------------------------------------------------- From: guy@galactica.it Subject: subscibe Date: 05 Nov 1996 18:19:06 -0100 I have tried 10 times to subscibe me to the mailing list: police@xmission.com but it was impossible due to the automatic reply system. I ask you please to subscibe me manualy my internet address is: guy@galactica.it this subscibe is very important for me and my friends here in Italy thank you.... bye Guido ------------------------------------------------------------------------------- From: "Khedron Espinoza" Subject: 56k modems Date: 05 Nov 1996 13:39:20 -0800 do you plan to upgrade to 56k modems when they come out?? ------------------------------------------------------------------------------- From: "Doran L. Barton" Subject: Re: 56k modems Date: 05 Nov 1996 13:36:55 -0700 At 01:39 PM 11/5/96 -0800, Khedron Espinoza wrote: >do you plan to upgrade to 56k modems when they come out?? I do believe I remember Pete Ashdown posting that Xmission was planning on getting the necessary digital connections to the phone company to do that as soon as it was available. -Fozz ============================================================================= Doran L. Barton = fozz@xmission.com && http://www.xmission.com/~fozz/; "You're spending too much time online when you start referring to going to the bathroom as downloading." ------------------------------------------------------------------------------- From: J!m Hepworth Subject: Re: 56k modems Date: 05 Nov 1996 15:42:01 -0700 At 01:36 PM 11/5/96 -0700, you wrote: >At 01:39 PM 11/5/96 -0800, Khedron Espinoza wrote: >>do you plan to upgrade to 56k modems when they come out?? > >I do believe I remember Pete Ashdown posting that Xmission was planning on >getting the necessary digital connections to the phone company to do that >as soon as it was available. I don't think he is refering to digital (ISDN) lines. I think he talking about the new "x2" technology that US Robotics just announced that does 56K over standard analog lines. Check out the following for more info: http://x2.usr.com/ -J!m encore@xmission.com ------------------------------------------------------------------------------- From: "Doran L. Barton" Subject: Re: 56k modems Date: 05 Nov 1996 15:47:32 -0700 At 03:42 PM 11/5/96 -0700, J!m Hepworth wrote: >At 01:36 PM 11/5/96 -0700, you wrote: >>At 01:39 PM 11/5/96 -0800, Khedron Espinoza wrote: >>>do you plan to upgrade to 56k modems when they come out?? >> >>I do believe I remember Pete Ashdown posting that Xmission was planning on >>getting the necessary digital connections to the phone company to do that >>as soon as it was available. > >I don't think he is refering to digital (ISDN) lines. I think he talking >about the new "x2" technology that US Robotics just announced that does 56K >over standard analog lines. That's what I'm talking about too. Pete mentioned that Xmission was going to be getting the necessary digital lines to do X2 technology. In order for an ISP to do X2, they need a digital trunk run in from the phone company which connects to (surprise) USRobitics equipment. IMO, X2s a joke. -Fozz ============================================================================= Doran L. Barton = fozz@xmission.com && http://www.xmission.com/~fozz/; "You're spending too much time online when you start referring to going to the bathroom as downloading." ------------------------------------------------------------------------------- From: J!m Hepworth Subject: Re: 56k modems Date: 05 Nov 1996 16:16:08 -0700 At 03:47 PM 11/5/96 -0700, you wrote: >>I don't think he is refering to digital (ISDN) lines. I think he talking >>about the new "x2" technology that US Robotics just announced that does 56K >>over standard analog lines. > >That's what I'm talking about too. Pete mentioned that Xmission was going to >be getting the necessary digital lines to do X2 technology. In order for an >ISP to do X2, they need a digital trunk run in from the phone company which >connects to (surprise) USRobitics equipment. > >IMO, X2s a joke. When they said 56K over analog lines I didn't realize the provider had to have a digital link and it was just the end user that has the analog line. I was just checking the specs on USR's web site and you are correct on that. Aren't all Xmissions modems USR's already? (courier's I believe) For those who want some detail. x2 will allow Xmission to transfer data to the user at 56K, but the user will only tranfer data back to xmission at 28.8K. For the internet (WWW) this is perfect since you send very little but recieve lots. This all sounds good, but unless you have a US Robotics modem you won't be able to use this new speed even when Xmission gets it. If you have a newer sporster modem you will just need a chip upgrade. If you have a Courier you will be able to just Flash the new x2 standard into your modem. As for a joke we'll just have to wait and see. I never get 33.6K connections as it is (usually 24-28.8). Luckily I have a courier and won't have to buy a new modem when it's available to try it out. If it works as they say, it will make a good interum step on the way to true digital. -J!m encore@xmission.com ------------------------------------------------------------------------------- From: "Delbert R. Phillips" Subject: Keep getting kicked off the net Date: 06 Nov 1996 17:53:21 -0700 Today I am experiencing difficulty in keeping a net connection more than 3 minutes or so. What is up? I have to re connect in the middle of downloading a page off the net. The message in windows 95 mentions "peer connection". Are you working on correcting it? It is annoying. As you know from our address we are running through the Provo Anex. Thank You drpatty@xmission.com ------------------------------------------------------------------------------- From: David Lewis Subject: Keep getting kicked off the net -Reply Date: 07 Nov 1996 08:27:41 -0700 I too am connecting to the Provo number and am getting disconnected almost every time I log on through PPP after varying amounts of time...I spoke with tech support at xmission and they suggested that it was "line noise" because I was "so far" away from the phone number I'm calling...well it's only 20 miles...if phone lines today are so bad that communication breaks down within only 20 miles, that's pretty sad... Anyone else having similar problems? How far are you from the number you are dialing in to? thanks, David. >>> "Delbert R. Phillips" 11/06/96 05:54pm >>> Today I am experiencing difficulty in keeping a net connection more than 3 minutes or so. What is up? I have to re connect in the middle of downloading a page off the net. The message in windows 95 mentions "peer connection". Are you working on correcting it? It is annoying. As you know from our address we are running through the Provo Anex. Thank You drpatty@xmission.com ------------------------------------------------------------------------------- From: "Timothy Little" Subject: Still cannot connect... Date: 07 Nov 1996 23:41:38 -7 I left a message with your Billing Dept at approx 9:30 PM, Wednesday November 6th -- and then called again at 4:30 PM the next day. I was then informed that my account was delinquent. That was a surprise, since I gave them my credit card number and it was charged on Oct 28th. Then again today (the 7th of November), I again gave them my credit card number and when trying to log on some 5 hours later, I am still unable to use the service. Please reply to this Wasatch.Com address or leave a telephone message telling me what is happening. Tim... ------------------------------------------------------------------------------- From: Stephen D Hancey Subject: NT 4.0 Date: 08 Nov 1996 07:47:19 -0700 Do you have any HELP for configuring NT 4.0 with Xmission?? ------------------------------------------------------------------------------- From: James Brigman Subject: DNS information Date: 13 Nov 1996 17:33:03 -0700 (MST) I have had to re-install Windows95 after s crash. I need the DNS information for the winsock.dll. Thank you. ------------------------------------------------------------------------------- From: J!m Hepworth Subject: Re: DNS information Date: 13 Nov 1996 17:47:02 -0700 At 05:33 PM 11/13/96 -0700, you wrote: >I have had to re-install Windows95 after s crash. I need the DNS >information for the winsock.dll. Thank you. primary: 198.60.22.2 secondary: 206.26.97.2 -J!m encore@xmission.com ------------------------------------------------------------------------------- From: James Brigman Subject: Re: DNS information Date: 13 Nov 1996 19:49:03 -0700 (MST) Thank you. I see now that the properties for the DNS settings wants a Host name. I know that the Domain name should be xmission.com but what should be the Host name. Or should I disable the DNS portion? Again thankyou. On Wed, 13 Nov 1996, J!m Hepworth wrote: > At 05:33 PM 11/13/96 -0700, you wrote: > >I have had to re-install Windows95 after s crash. I need the DNS > >information for the winsock.dll. Thank you. > > primary: 198.60.22.2 > secondary: 206.26.97.2 > > -J!m > encore@xmission.com > > ------------------------------------------------------------------------------- From: "Tony" Subject: NFS Server or NIS Server? Date: 15 Nov 1996 10:57:15 -0700 I downloaded some demo version of DiskAccess from Intergraph, and it's asking for either an NIS Domain Name or a PCNFSD Server Does xmission support either of these? Thanks in advance! - T Here's some quotes from their help file: NIS Domain Name specifies the Network Information Service (NIS) domain name to broadcast. DiskAccess broadcasts for NIS servers to all machines on the local area network (LAN) to find an NIS server within the NIS domain name specified. The NIS Client portion of DiskAccess requests the NIS server to return a matching value given a key. For example, if the client is accessing a password database, the key used is a username and the matching value returned is an entry in the password database, which contains the user ID (UID), group ID (GID), and password for a user. The client then tries to match the password typed by the user with the password from the returned value and if it matches, UID and GID are returned. To return secondary GIDs, the client performs a similar operation on the group database and returns a list of GIDs for the user if available. And another quote: PCNFSD Server PCNFSD Server specifies the name of a remote system used to establish your user and group ID. This server runs a process called PC-NFS daemon (PCNFSD). The PCNFSD server is frequently the same as the NFS server, but can be any system on the network. The PCNFSD server compares the username and password with its password file. If the username and password match one in the file, the PCNFSD server returns the corresponding user ID (UID) and group ID (GID), which are used to connect to the remote NFS server system. ------------------------------------------------------------------------------- From: Bill King Subject: Huh? Message from HARAN at SYDVM1 (fwd) Date: 15 Nov 1996 15:56:58 -0700 (MST) I have gotten several messages just like this in the last few days. Can anyone enlighten me as to what this means, where it comes from, and if I should pay any attention to it? TIA, --Bill King .sig shows an old guy juggling 5 balls in a pattern that every juggler knows is completely bogus. ---------- Forwarded message ---------- Vacation 11th Nov - 25th Nov. Will access profs intermittantly. The mail you sent has arrived. This message was sent by the SAFE automatic machine: do not reply. ------------------------------------------------------------------------------- From: James Brigman Subject: Win95 help Date: 15 Nov 1996 17:12:13 -0700 (MST) I have put the DNS information that you have previously given to me into the winsock.dll for widows 95 using the network control panel. It requires that a host and domain names be input also. Please advise what to put in these fields. Again thank you. ------------------------------------------------------------------------------- From: J!m Hepworth Subject: Re: Win95 help Date: 15 Nov 1996 22:02:37 -0700 At 05:12 PM 11/15/96 -0700, you wrote: >I have put the DNS information that you have previously given to me into >the winsock.dll for widows 95 using the network control panel. It requires >that a host and domain names be input also. Please advise what to put in >these fields. Again thank you. Under Control Panel/Network/TCP-IP/Properties/DNS Config Select Disable DNS. Now do the following: Control Panel Dial-Up Networking Right click on Xmission Icon Select Properties Select Server Type Type of Dial-up should be PPP Logon to Network should be off (MS recommended) NetBUEI should be off (MS recommended) IPX/SPX should be off (MS recommended) TCP/IP should be ON Select TCP/IP settings Server assigned IP address should be ON Specify name server addres should be ON Primary DNS: 198.60.22.2 Secondary DNS: 198.60.22.22 (NEW!) That should do it. -J!m encore@xmission.com ------------------------------------------------------------------------------- From: MDA Subject: Any hope ? Date: 22 Nov 1996 00:18:51 +0000 Are things going to get better anytime soon ? For quite a while now I've been having A LOT of trouble with newsgroups loading, getting hung up on, connecting, etc. .It's getting a little old and from talking to other people they're having the same problems so I know it isn't on my end. I've been on Xmission now for over two years and I would like to remain but........... mallen ------------------------------------------------------------------------------- From: David Lewis Subject: Any hope ? -Reply Date: 25 Nov 1996 10:40:50 -0700 I haven't been looking at the newsgroups, but I'm always getting disconnected EVERY time I connect...I have to reconnect several times each night...I was told it was "line noise" but I'm just not buying that anymore...my previous ISP was about the same distance and I hardly ever got disconnected... I have to admit, I don't ever get a busy signal, but getting disconnected frequently is really more of a pain... Any ideas? David. >>> MDA 11/22/96 12:18am >>> Are things going to get better anytime soon ? For quite a while now I've been having A LOT of trouble with newsgroups loading, getting hung up on, connecting, etc. .It's getting a little old and from talking to other people they're having the same problems so I know it isn't on my end. I've been on Xmission now for over two years and I would like to remain but........... mallen