Search results for query: *

OK, so I sort of figured it out. I was researching this further and saw a Cisco doc that happened to mention the path BACK from the other network. It occurred to me that if the host on the other network doesn't know how to route back to the host in the main network, then ... (duh) At any rate...

The routing statement I added to 10.1.1.168 was to test the ability of the 2611 to actually route amongst the 2 networks. The default gateway of any host in the 10.1.x.x network is 10.1.1.1 (a Cisco PIX 501). Its default gateway is our Cisco 2620, which is connected to the MCI T-1. Without that...

Just to clarify ... The 1720 is on the far end of the other network, but is not involved at this point. The ping test I was trying to run would look somewhat like this: Host (in main network) --> 2611 --> Host (in other network) It looks like the traffic gets from the first host to the 2611...

In our office, we have 2 different networks, connected to the Internet by 2 different T-1s. (The T-1s are from different providers, too.) I've been tasked with developing a setup that will allow our Internet traffic (outgoing) to go out the other T-1 if the main one is down. Our main router is...

I have an OEM-type (LSI, I think) drive cage with 10 18GB SCSI hard drives in it. It's currently attached to my server with an Adaptec 2944UW adapter, since it needs to be HVD. Anybody know if there's a RAID controller out there that will handle HVD SCSI connections? Seems that everywhere I...

I have this issue on a couple of my Windows 2000 Servers. When the server starts up (rebooted, etc.), I get an event ID 7031 in the system log: "The SNMP Trap Service service terminated unexpectedly. It has done this (x) time(s). The following corrective action will be taken in 0...

Not the .au variety of Google, but yes, numerous times on this topic. Haven't found anything that addresses this specific topic yet. If you have, it would be appreciated.

It's interesting the different options for handling the trapped messages. Most of the products/services I'm investigating can reject, quarantine (in some way, usually by sending to a mailbox for review) or tag the message. Currently, we drop the vast majority of the spam into our tarpit for...

We currently host several mail servers which serve a number of clients. We're finding that we spend way too much time adjusting our filters to prevent spam (they're reasonably effective, but it's time-consuming to do so). So we're considering three overall scenarios: 1. Outsource e-mail...

I have a client who's got one user having problems with succesfully sending e-mail through our server. We use SMTP AUTH to prevent relaying, and this particular user moves around a lot, so putting his IP address into a whitelist isn't practical. I've done some packet captures to see exactly...

It's much easier in AD because you're dealing with a domain. Domains can have multiple domain controllers, so simply setting up another machine as a domain controller would copy all the accounts. Of course, since you're trying to do a 1-for-1 replacement (same machine name, etc.), all that goes...

If you can find a tool, that'd probably be best, but I didn't find one when I went looking the other day. If you really have some time on your hands (unlikely, but just thought I'd throw it out there), you might try messing around with copying the SAM file. That should contain all the usernames...

Strange. Hopefully the auditing will provide you with some useful information. Without a lockout policy, it doesn't really make any sense, but at least you'll have somewhere else to look.

You can permit relaying from specific IP addresses or address ranges. That might be your best bet.

Do you have any sort of auditing enabled? That would at least show when users log on, and would show failed logon attempts. Also, is there an account lockout policy? For example, you might have one that locks an account out after 5 unsuccessful attempts.

Wouldn't you need to set up RRAS to do this? It appears you want to make the server act as a router. RRAS (Routing and Remote Access Service) will allow you to do that, I believe. Otherwise, you have a machine that can send and receive on two different networks but won't route packets between...

You're talking about taking accounts from a standalone Windows 2000 Server and moving them to another standalone Windows 2000 Server. At least that's how I read your original post. ("I installed windows2000 in standalone mode with workgroup.") So dcpromo won't do anything in terms of...

I imagine you're talking about having to reset passwords for accounts that are used through IIS, right? (In other words, accounts that are used to log onto a web site.) Did you check to see if the accounts are set to have "Password never expires" checked? It's possible that the...

Unless you specifically opened port 137 for any of your IPs, it's being blocked by default. That's the beauty of a firewall -- everything is blocked unless you specify otherwise.

We recently purchased some new computers for our developers. I built one of them up from scratch (they're running Windows 2000 Professional) and then used sysprep and Ghost to deploy the final image to the other computers. In addition to IE6, Windows 2000 SP4 and all the latest patches, the...