Recent content by Mac2118

Hello everyone, it's me again. We could ping the connection, 100% success rate. But we're still having a problem getting the connection established. Below I have copied and pasted the information from the log relating to this issue. Dec 20 2008 11:37:03 302013: Built inbound TCP connection...

The problem was what I thought it was. I also had a few other people agree with me that the reason it wasn't communicating was because there was no gateway address configured. once that was put in communication was possible. Thank you to everyone that helped along this proces!

I connected a spare laptop to that connection with the same internal IP address. I tried to reach the outside world and nothing. I added in the gateway: nothing. I then added in the default DNS server and everything worked perfectly. I just got a phonecall from the company we purchased this...

there is no return traffic. there is no firewall on this unit, and there is no way for me to test its connection to the internet since it's not windows/linux/unix/etc based. I spoke to a few Cisco consultants and they all agree with me that the PLC is not configured correctly. we will be...

I am still showing: 302013: Built inbound TCP connection 394371 for outside: xx.xx.xx.24/25003 (xx.xx.xx.24/25003) to inside: 192.168.1.47/2222 (xx.xx.xx.232/2222) then about 2 minutes later I see 302014: Teardown TCP connection 394518 for outside xx.xx.xx.24/25208 to inside...

I apologize, I spoke too soon. I configured the logging for lvl 5 on the "History" and "Monitor" settings I now see: Syslog logging: enabled Facility: 20 Timestamp logging: disabled Standby logging: disabled Console logging: disabled Monitor logging: level notifications, 0...

I do not believe that we have logging configured. when I run the "sho log" command I get the following: Syslog logging: enabled Facility: 20 Timestamp logging: disabled Standby logging: disabled Console logging: disabled Monitor logging: disabled Buffer logging...

I just want to throw this into the mix just in case. I thought the problem could have been that I was using an unallocated public IP. I called to verify that I was using the right address and we got to talking about what I was planning on doing. Our setup is the T1 comes into a Cisco router...

as a little test, I took the .231 public IP address that "did" ping on other sites and removed the info for that and the .232 ip that I am having problems with. I replaced all information in the .231 with the .232 info. I am still showing no ping information for that device. I am really at...

He told me that he's connected with other customers before. On his log it shows that he can send packets to the machine, but the machine will not reply back out. I for one cannot see how that can be when the ports that it needs are opened up and ready to go. he can contact the machine I can...

I caught the inbound connection: 302013: Built inbound TCP connection 394371 for outside: xx.xx.xx.24/25003 (xx.xx.xx.24/25003) to inside: 192.168.1.47/2222 (xx.xx.xx.232/2222) then about 2 minutes later I see 302014: Teardown TCP connection 394518 for outside xx.xx.xx.24/25208 to inside...

I set up the logging in the PDM logs and I missed the initial connection, but it does state: 302014: Teardown TCP Connection 390268 for outside: xx.xx.xx.24/20706 to inside: 192.168.1.47/2222 duration 0:02:01 bytes 0 SYN Timeout

Will that work even though they are not connecting through VPN? The only VPN I am familiar with was the initial setup of the VPN and having users make a connection with the Cisco VPN Client and access all of the network resources that way.

I don't mean to sound "Noobish", but how would I go about looking at packet traffic on the firewall through PDM? I brought up the PDM in the Monitoring tab, but I am unsure of where to go from there. I don't know if I should look under incoming or outgoing. I'm thinking I need outgoing.

I have been working with a company to establish Port Address Translation between a piece of machinery here to their location. The internal address of the PLC of the machine is 192.168.1.47. Below I have what our current configuration is (minus password and VPN setup for security reasons, and I...