Greybear

I dont doubt you were told that the 2100 would work with NT drivers. Who told you? Sales, or Megabit? Sales is a problem. The management is well aware of sales making promises that arent true and steps are being taken at this very moment to completely stop that entire situation. I can agree that in a situation (If I understand it correctly) that youve presented, that you got screwed by misinformation, and I am %100 behind you. I would ask you to understand where the tech is coming from on the other end, as they have no way of shipping you a temp. 675, and tracking it to make sure they get it back. People can simply refuse to return it and thats the last they see of it sadly enough. That is also being changed, so at some future time, it might indeed be possible to "loan out" 675's. But again, USWest is most likely thinking "who do we have to ship out a $300 router for Intel's screw up?" While that does leave the customer at a bad end (which I disagree with completely) I can understand the mentality (That were working hard to change) behind that desision. Not to mention the extreme possibility for fraud. As for the Car analogy, Again, if thats what happened to you, it sucks. I can only say that there are people who are working to change all of this, and high officials who know exactly how badly it bites to be a jilted customer, because techs keep reminding them. It will get better, for whats its worth. Greybear

I think you can find Hearts for BeOS 5.0 You could duel-boot into Win2k, and hit BeOS for your Hearts fix. It boots in 15 seconds. In and out before the boss walks by. <grin> [This message has been edited by Greybear (edited 16 May 2000).]

Alot of us here, (myself included,) would be inclined to agree. Greybear

a few more clerifications: The telephone company (which includes Mega*.*) is seperate from the ISP, by Federal Law. The telephone company (and thus mega*)doesnt care if you use full bandwith the entire time youre online. Its like making a 13 hour local phone call. Who cares? The ISP however, might see it diffrently. Youre using *Their* bandwith and their servers to hit the net. If you clog their servers, then no one else gets on. You can count the fear of exsessive bandwith consumption out of the list as well. Personally I find it amusing that people want a free 675 because of the drivers for the 2100. This would be similar to buying a ford with the express knowledge that the ford doesnt have power windows and there are no garantees it ever will. After a few months, you take it back and express extreme dissatisfaction with Ford because it doesnt give you the option to upgrade to power windows. In fact, you think youre entitled to a Dodge ram for your troubles, at the cost of the Ford dealership. I cant believe it when I hear my cubemates tell me how they just talked to someone who was completely rude, demanding a product that costs $200 more then their router because they were too cheap to buy the 675 in the first place, and now they changed their minds. Last note: Cisco hasnt committed to doing a driver for the 605 at all. Greybear

MacOS 9 is just about as bad. Can we say "Open Transport Issues?" "Mac DHCP Freeze?" "supposed to be fixed in OS 7x, 8.5, 8.6, and 9.0 but it seems to keep happening?" I know some Mac afficandos that are begining to think that unless OSX has Open transport issues, its not a real Mac Platform. Greybear

Hi.. there is a link to a prior post I did at the bottom of teh page. A few things first... To clerify, I work for MegaLAN, the network oriented devision that configures the 675. There are 10 people on my team as opposed to the 60 or so that are on at any given time for megabit, which handles the Cisco 605, 675, and Intel 2100. A few things I want to point out, since it doesnt seem to be clear to some people: #1. Internet connection sharing. When I worked on Megabit a while back, I used to get calls from people trying to network the 605 or the 2100 through ICS. I still get those, when they somehow stumble into my que after being told that MegaLAN support them. Each and every person that Ive ever talked to had reported that ICS with the 2100 or 605 has completely hosed windows. They had to do a full Fdisk, Format and Reinstall. The reason for this is really very simple. *Youre not installing a Modem.* The 605 and 2100 are *Routers* and they dont dial up, the dont operate in an even remotely similar way to an analog modem, and ICS wasnt designed for a Router. Its modemville, baby. Hope this helps get rid of some of the conspiracy theories Ive heard way to often. #2. We here at tech support have been told consistantly that the 2100 would have win2k drivers publicly available on the 8th of this month on the uswest website. As you might notice, its currently the 16th, and still no drivers. I received word *5 minutes ago* that Intel has waffled, and they are not, as was previouslly indicated, doing a public beta test. They are conducting a *private* beta test. This bites for us as well as you, because not only have we been telling the customers that call that the drivers would be available over a week ago, but now we have to get back on the phones and explain to generally ticked off people that we wernt lying to them, We were told by intel that we would have drivers and now they changed their minds. Intel has NOW told us that the public drivers will be out sometime in August. We're not happy about it either. http://www.ntcompatible.com/ubb/Forum3/HTML/002427.html

You have a port issue. your router is acting as a partial firewall by having ports closed by default. Contact the maker of the router or whoever sold you the router and ask them about the problem. Most likly NAT related. They should be able to help you get into the routers OS or software and open the ports youre trying to access. Heads up though. Have a list of ports beforehand, because nothings worse than getting a call from someone telling you they need to open some ports and getting them in there, giving the command, saying "ok, type in the port here" and they say "uhhhhhh.. I dont know it." Greybear

Sorry, Ive been away. Yes, it should be perfectly possible. If you have the server connect and have the workstations go through NAT, yes. It shouldnt matter if its a dedicated line (T-1, xDSL, ISDN, etc.) or a modem as long as the connection is there. The main problem is the setup of routing and remote access, (which I havent played with, but I know it would work, thats its primary purpose). I have heard that if you check the box marked "enable IP forwarding" in NT server, thats about it(Again, I dont know for sure,) And win2k will be diffrent. But your question was should it work... and to take all of my long winded answers out of it and get to the point: Yes. Now as for the NAT, Hmmmm. Thats where Im lost. Ive worked with NAT but to tell you the truth, I dont know f Server has NAT capabilities, or where they would be. Id imagine it would, so if you know, tell me! Greybear

It should be possible. Ive seen it done on NT every day and have helped people with it myself. Im unsure of the total details but heres how it should work. You have 2 NICs... the inside NIC (LAN) and the outside NIC (WAN or connection to xDSL) Depending on whether your ISP had you set up with a Dynamic IP or a Static IP, you would set the outside NIC accordingly. Set the inside NIC with the Static IP of the DHCP server, you've alreasy set the DHCP server pool, and you've got your LAN. Under Admin Apps, theres remote access and routing, which I beleive does the same job that IP routing does in NT. I havent played around with it beause of my setup but It should be possible to enable IP forwarding through there, set the gateway through DHCP of all the workstations to the inside NICs IP, set the inside NICs gateway to the outside NICs IP, and have the outside NICs IP set to your default gateway assigned by our ISP. This should enable the packets passed from the workstations to do a massage game of trade off right through to the ISP, where its sent back with the info requested to the said workstation. A little confusing but if these concepts arent clear, Im wondering what someone would be doing with win2k Advanced server. Greybear

Does anyone know if there is an application built into Windows 2000 server that would monitor connections made via telnet to a running telnet server? Im talking server side, not client side. If anyone has any info or maybe even a 3rd party solution, please let me know. Thanks!

If youre using AOL 5.0 be careful because Ive gotten alot of customer calls at my work where AOL installs its own TCP/IP stack and it completly hoses the TCP/IP in windows. As a result, your network, DSL, etc, anything that uses TCP/IP wont work as the version AOL installs is specifically written for AOL use, and it completely replaces the windows version. Now, Ive talked to people who have had this happen and people who havent. Im not sure why it messes with some people and doesnt with others. I do know this is the basis of the class action Lawsuit that was levied againts AOL. The only known cure for this (That I know of anyway) is to uninstall AOL and uninstall and reinstall DUN (in 98), TCP/IP in win2k. greybear

I use a Webramp 700s Firewall for my FTP server on my DSL line. Its pretty good in my opinion, and its hardware based which I like more than software based. Its got pretty good security, supports NAT and DHCP serving, PAT, and a number of other mesures. If youre interested, try http://www.rampnetworks.com/products/700s/index.html Greybear

I have noticed several posts here in the past regarding the Cisco 605/Intel 2100 drivers under win2k. We just received word on what the status is. Intel will be releasing the drivers in May and Uswest will be supporting them in end of may/ begining of june. That is *only* for the Intel 2100. Cisco is still undecided on drivers for win2k and is still maintaining the "Dont count on it" stance. Now, to clear some things up. In most of the posts Ive read, its stated that Cisco "sold the 605 to Intel." Thats completely incorrect. USWest was forced to drop the contract with Cisco as Cisco discontinued the production of the 605s. USWest didnt have much of a choice. USWest also doesnt have a choice on whether or not drivers are released for one OS or another. I, Personally, have had people curse me out on the phone when I try to explain to them that not only is WIN2k not supported, neither is Linux, Unix, FreeBSD, BeOS, etc, because of lack of drivers, training and a million other factors. Its not like we have they drivers and just arent giving them out. You dont go to compUSA (I wouldnt anyway) and buy a 3com NIC and then scream at CompUSA when the drivers in the box dont arent written for your OS. You scream at 3com. Not to mention that USWest has been very forward from what I can see that while come dsl routers (and they are level 3 routers, not modems.) will work with diffrent OSes, We dont support anything other than win9x and macOS 7.5-9. Now. If you want networking capabilities, you can use the 2100 when the drivers come out but you'll have to use a proxy server and USWest doesnt support that because of the high number of proxy servers available out there. I dont want to have to remember 300 diffrent pices of software either so Im behind USWest on that one. Myself and the other techs on MegaLAN will, however, happily support peer-to peer networking of the 675, and even though we dont support a client/server relationship offically, all 10 techs (myself included) have unoffically helped everyone who calls in with this configuration as much as possible. Even though we might not know the answer, We'll help you with what we *do* know. Any other questions, feel free to ask. I check every once in a while and will respond when I can.

I work for USWeat MegaLAN, the section on Megabit that handles cisco 675's on networks. I used to do support for the cisco605 and intel 2100, and I can assure you there there is *no* drivers for either. Reason being that cisco has discontinued the production of the 605 and thus wont be upgrading the drivers, and Intel hasnt stated any desire to do so as of yet. There is not only no word of desire, but actual discussion as to *never* providing drivers. Which is unfortunite, because I run 2kadvanced server at home, but I have GTE. And USWest makes it clear that they dont support win2k in any way shape or form, along with UNIX, Linux, Novell, etc. Your best bet is to exchange the 2100 for a Cisco 675 external, because win2k has no problem with NIC drivers. If you call Megabit, we will tell you as much. Quote: Originally posted by ChaNce: Hey, has anyone got this dsl card to work with win2k? I have a USWEST dialup connection, and would like to use it with win2k. Help?