Jump to content

cware

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About cware

cware's Achievements

0

Reputation

  1. Hey IcemanND, I finally got things under control in the office and got back to this. I now have access working again. The problem? Can you say Symantec? Turns out the Symantec package corporate gave to me had a firewall buried down inside it that I didn't know about. Once I knew that and was able to get down to it, I was able to add rules to allow ports 139 and 445. I want to thank you for your efforts to help me out on this issue. Thank you, Chris
  2. Yes, wireshark from both sides. The microsoft-ds did not show on the server machine. Tracert returns the correct IP when run with the name, so it's picking up the information from the DNS server.
  3. I wish that was the case. There are no software firewalls installed on the machine and all IPs in the Pix were updated. There were no changes to the ACL in the Pix, so that shouldn't be causing this problem. I ran traffic through wireshark yesterday and noticed that the TCP microsoft-ds traffic never made it to the machine and can't figure out why for the life of me.
  4. Hello, I have a problem with one of my servers that showed up after having to switch it's IP address. It's running Windows Server 2000. It's utilized as our web server. This machine is in my DMZ and all firewall rules (Cisco Pix) have been updated and internet connectivity is working. This problem did not exist prior to the change in IP and nothing else was changed on this machine. The problem I'm having is that I am unable to map a drive (either through the Windows interface or the Net Use command) to this machine from any computer (inside or DMZ). When using net view from another machine in the DMZ, the machine shows up in the list for that workgroup. When I do a net view \\server, I get: "System error 53 has occurred. The network path was not found." I have it in our internal DNS server with the correct IP. I am able to ping the machine both by name and IP from inside and DMZ, as well as perform a nslookup successfully. I have tried mapping using the name as well as the IP and both give the same error. I am able to map drives to any other computer in the DMZ from inside or other DMZ. I can also map a drive from the machine in question to other machines in the DMZ. File and print sharing is enabled. I'm about out of ideas to track down the problem. Any ideas would be greatly appreciated. Thanks, Chris
×
×
  • Create New...